This site is the archived OWASP Foundation Wiki and is no longer accepting Account Requests.
To view the new OWASP Foundation website, please visit https://owasp.org

Difference between revisions of "OWASP DeepViolet TLS/SSL Scanner"

From OWASP
Jump to: navigation, search
(Undo revision 218887 by Miltonsmith (talk))
Line 5: Line 5:
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
{| style="padding: 0;margin:0;margin-top:10px;text-align:left;" |-
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="border-right: 1px dotted gray;padding-right:25px;" |
 
<span style="color:#ff0000">
 
Instructions are in RED text and should be removed from your document by deleting the text with the span tags. This document is intended to serve as an example of what is required of an OWASP project wiki page. The text in red serves as instructions, while the text in black serves as an example. Text in black is expected to be replaced entirely with information specific to your OWASP project.
 
</span>
 
  
 
==OWASP DeepViolet TSL/SSL Scanner Code Project==
 
==OWASP DeepViolet TSL/SSL Scanner Code Project==
 
What is DeepViolet?
 
  
 
DeepViolet is a TLS/SSL scanning library/tool written in Java.  Use DeepViolet from the command line in your own *nix or Windows scripts. Alternatively, use the graphical user interface to scan HTTPS web servers from your desktop or include the DeepViolet API to include TLS/SSL scanning in your applications. Check server certificate trust chains, revocation status, check certificates for pending expiration, weak signing algorithms and more.
 
DeepViolet is a TLS/SSL scanning library/tool written in Java.  Use DeepViolet from the command line in your own *nix or Windows scripts. Alternatively, use the graphical user interface to scan HTTPS web servers from your desktop or include the DeepViolet API to include TLS/SSL scanning in your applications. Check server certificate trust chains, revocation status, check certificates for pending expiration, weak signing algorithms and more.
  
Why Develop a New Scanning Tool?
+
==Description==
  
 
Great free and commercial products exist in the TLS/SSL scanning space.  The reason to build a new TLS/SSL scanning tool was, 1) learn more about TLS/SSL protocols, crypto, and trust management.  In fact, learn everything there is to know about the brief moment a web browser connects to a secure web server, 2) develop a tool in Java.
 
Great free and commercial products exist in the TLS/SSL scanning space.  The reason to build a new TLS/SSL scanning tool was, 1) learn more about TLS/SSL protocols, crypto, and trust management.  In fact, learn everything there is to know about the brief moment a web browser connects to a secure web server, 2) develop a tool in Java.
  
==Description==
+
'''Project requirements''': Java SE 8. Tested on OS X 10.11.5 El Capitan and
<span style="color:#ff0000">
+
Windows 10. GitHub includes Travis CI Build Badge to provide code compile confidence.
This is where you need to add your more robust project description. A project description should outline the purpose of the project, how it is used, and the value it provides to application security. Ideally, project descriptions should be written in such a way that there is no question what value the project provides to the software security community. This section will be seen and used in various places within the Projects Portal. Poorly written project descriptions therefore detract from a project’s visibility, so project leaders should ensure that the description is meaningful. 
 
</span>
 
 
 
The Code Project Template is simply a sample project that was developed for instructional purposes that can be used to create default project pages for a Code project. After copying this template to your new project, all you have to do is follow the instructions in red, replace the sample text with text suited for your project, and then delete the sections in red. Doing so should make it clearer to both consumers of this project, as well as OWASP reviewers who are trying to determine if the project can be promoted to the next category. The information requested is also intended to help Project Leaders think about the roadmap and feature priorities, and give guidance to the reviews as a result of that effort.
 
 
 
Creating a new set of project pages from scratch can be a challenging task. By providing a sample layout, with instructional text and examples, the OWASP Code Project Template makes it easier for Project Leaders to create effective security projects and hence helps promote security.
 
  
 
==Licensing==
 
==Licensing==
  
Apache 2.0 License (fewest restrictions, even allowing proprietary modi cations and
+
This library is free software: you can redistribute it and/or modify it under the terms of the [https://github.com/spoofzu/DeepViolet/blob/master/LICENSE Apache License, Version 2.0]. You can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.
proprietary forks of your project)
 
 
 
<span style="color:#ff0000">
 
A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see [https://www.owasp.org/index.php/OWASP_Licenses OWASP Licenses]. While OWASP does not promote any particular license over another, the vast majority of projects have chosen a Creative Commons license variant for documentation projects, or a GNU General Public License variant for tools and code projects.  This example assumes that you want to use the AGPL 3.0 license.
 
</span>
 
 
 
This program is free software: you can redistribute it and/or modify it under the terms of the [http://www.gnu.org/licenses/agpl-3.0.html link GNU Affero General Public License 3.0] as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.  OWASP XXX and any contributions are Copyright &copy; by {the Project Leader(s) or OWASP} {Year(s)}.
 
  
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
 
| valign="top"  style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
  
 
== Project Resources ==
 
== Project Resources ==
<span style="color:#ff0000">
 
This is where you can link to the key locations for project files, including setup programs, the source code repository, online documentation, a Wiki Home Page, threaded discussions about the project, and Issue Tracking system, etc.
 
</span>
 
  
 +
[https://github.com/spoofzu/DeepViolet Source Code]
  
https://github.com/spoofzu/DeepViolet
+
[https://github.com/spoofzu/DeepViolet/releases Release Binaries]
  
[https://github.com/SamanthaGroves Compiled DLLs]
+
[https://github.com/spoofzu/DeepViolet/issues Issue Tracker]
  
[https://github.com/SamanthaGroves Source Code]
+
[https://github.com/SamanthaGroves Slide Presentation tbd]
  
[https://github.com/SamanthaGroves Documentation]
+
[https://github.com/SamanthaGroves Video tbd]
  
[https://github.com/SamanthaGroves Wiki Home Page]
+
== Project Leader(s) ==
  
[https://github.com/SamanthaGroves Issue Tracker]
+
email:[[[email protected] |Milton Smith ]]
 +
twitter:[https://twitter.com/spoofzu @spoofzu]
  
[https://github.com/SamanthaGroves Slide Presentation]
+
| valign="top"  style="padding-left:25px;width:200px;" |
 
 
[https://github.com/SamanthaGroves Video]
 
 
 
== Project Leader ==
 
<span style="color:#ff0000">
 
A project leader is the individual who decides to lead the project throughout its lifecycle. The project leader is responsible for communicating the project’s progress to the OWASP Foundation, and he/she is ultimately responsible for the project’s deliverables. The project leader must provide OWASP with his/her real name and contact e-mail address for his/her project application to be accepted, as OWASP prides itself on the openness of its products, operations, and members.
 
</span>
 
 
 
Project leader's name (s)
 
 
 
[[[email protected] |Milton Smith ]]
 
  
 
== Related Projects ==
 
== Related Projects ==
<span style="color:#ff0000">
+
tbd
This is where you can link to other OWASP Projects that are similar to yours.
 
</span>
 
 
 
* [[OWASP_Code_Tool_Template]]
 
* [[OWASP_Documentation_Project_Template]]
 
  
 
==Classifications==
 
==Classifications==
Line 95: Line 59:
 
   |}
 
   |}
  
| valign="top"  style="padding-left:25px;width:200px;" |
 
 
BUILDER PROJECT
 
  
 
== News and Events ==
 
== News and Events ==
<span style="color:#ff0000">
+
* [17 May 2016] Beta4 Release Candidate is available for download.  See [https://github.com/spoofzu/DeepViolet/releases/tag/1.4.000 release notes] for detail.
This is where you can provide project updates, links to any events like conference presentations, Project Leader interviews, case studies on successful project implementations, and articles written about your project.
 
</span>
 
* [18 Dec 2013] 1.0 Release Candidate is available for download.  This release provides final bug fixes and product stabilization. Any feedback (good or bad) in the next few weeks would be greatly appreciated.
 
* [20 Nov 2013] 1.0 Beta 2 Release is available for download. This release offers several bug fixes, a few performance improvements, and addressed all outstanding issues from a security audit of the code.
 
* [30 Sep 2013] 1.0 Beta 1 Release is available for download.  This release offers the first version with all of the functionality for a minimum viable product.    
 
  
 
|}
 
|}
  
 
=FAQs=
 
=FAQs=
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
Following are various frequently asked questions.
<span style="color:#ff0000">
 
Many projects have "Frequently Asked Questions" documents or pages. However, the point of such a document is not the questions. ''The point of a document like this are the '''answers'''''. The document contains the answers that people would otherwise find themselves giving over and over again. The idea is that rather than laboriously compose and post the same answers repeatedly, people can refer to this page with pre-prepared answers. Use this space to communicate your projects 'Frequent Answers.'
 
</span>
 
  
 
==How can I participate in your project?==
 
==How can I participate in your project?==
Line 122: Line 75:
  
 
= Acknowledgements =
 
= Acknowledgements =
 +
tbd
 +
 
==Volunteers==
 
==Volunteers==
  
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
tbd
<span style="color:#ff0000">
 
The success of OWASP is due to a community of enthusiasts and contributors that work to make our projects great. This is also true for the success of your project.
 
Be sure to give credit where credit is due, no matter how small! This should be a brief list of the most amazing people involved in your project.
 
Be sure to provide a link to a complete list of all the amazing people in your project's community as well.
 
</span>
 
  
The OWASP Security Principles project is developed by a worldwide team of volunteers. A live update of project  [https://github.com/OWASP/Security-Principles/graphs/contributors contributors is found here].
+
= Road Map and Getting Involved =
  
The first contributors to the project were:
 
  
* [https://www.owasp.org/index.php/User:Clerkendweller Colin Watson] who created the OWASP Cornucopia project that the template was derived from
 
* [https://www.owasp.org/index.php/User:Chuck_Cooper Chuck Cooper] who edited the template to convert it from a documentation project to a Code Project Template
 
* '''YOUR NAME BELONGS HERE AND YOU SHOULD REMOVE THE PRIOR 3 NAMES'''
 
 
= Road Map and Getting Involved =
 
 
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
 
<span style="color:#ff0000">
 
A project roadmap is the envisioned plan for the project. The purpose of the roadmap is to help others understand where the project is going as well as areas that volunteers may contribute. It gives the community a chance to understand the context and the vision for the goal of the project. Additionally, if a project becomes inactive, or if the project is abandoned, a roadmap can help ensure a project can be adopted and continued under new leadership.
 
Roadmaps vary in detail from a broad outline to a fully detailed project charter. Generally speaking, projects with detailed roadmaps have tended to develop into successful projects. Some details that leaders may consider placing in the roadmap include: envisioned milestones, planned feature enhancements, essential conditions, project assumptions, development timelines, etc. You are required to have at least 4 milestones for every year the project is active.
 
</span>
 
 
==Roadmap==
 
==Roadmap==
  
This Java project is operational. Deliverables include, 1) binary to perform TLS/SSL scanning
+
This project is already operational and includes a number of powerful features. Deliverables include, 1) binary to perform TLS/SSL scanning
 
from command line, 2) binary to perform TLS/SSL scanning from desktop, 3) binary API
 
from command line, 2) binary to perform TLS/SSL scanning from desktop, 3) binary API
interfaces to include TLS/SSL scanning in other projects. Project includes basic
+
interfaces to include TLS/SSL scanning in other Java projects. Project includes basic
documentation. Project requirements: Java SE 8. Tested on OS X 10.11.5 El Capitan and
+
documentation.  
Windows 10. GitHub includes Travis CI Build Badge to provide code compile con dence
 
 
 
This project is already operational and includes a number of powerful features. A number of
 
improvements could be made but I would like to build and engage a community, see how they
 
use DeepViolet, then determine the best roadmap.
 
 
 
 
 
 
 
  
 +
Project requirements: Java SE 8. Tested on OS X 10.11.5 El Capitan and
 +
Windows 10. GitHub includes Travis CI Build Badge to provide code compile confidence.
  
As of <strong>November, 2013, the highest priorities for the next 6 months</strong> are:
 
<strong>
 
* Complete the first draft of the Code Project Template
 
* Get other people to review the Code Project Template and provide feedback
 
* Incorporate feedback into changes in the Code Project Template
 
* Finalize the Code Project template and have it reviewed to be promoted from an Incubator Project to a Lab Project
 
</strong>
 
 
Subsequent Releases will add
 
<strong>
 
* Internationalization Support
 
* Additional Unit Tests
 
* Automated Regression tests
 
</strong>
 
  
 
==Getting Involved==
 
==Getting Involved==
Line 189: Line 107:
 
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
 
Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.
 
===Feedback===
 
===Feedback===
Please use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
+
Please send your comments to the project leader(s) or post it as a [https://github.com/spoofzu/DeepViolet/issues project issue].
<ul>
 
<li>What do like?</li>
 
<li>What don't you like?</li>
 
<li>What features would you like to see prioritized on the roadmap?</li>
 
</ul>
 
 
 
=Minimum Viable Product=
 
<span style="color:#ff0000">
 
This page is where you should indicate what is the minimum set of functionality that is required to make this a useful product that addresses your core security concern.
 
Defining this information helps the project leader to think about what is the critical functionality that a user needs for this project to be useful, thereby helping determine what the priorities should be on the roadmap.  And it also helps reviewers who are evaluating the project to determine if the functionality sufficiently provides the critical functionality to determine if the project should be promoted to the next project category. 
 
</span>
 
 
 
The Code Project Template must specify the minimum set of tabs a project should have, provide some an example layout on each tab, provide instructional text on how a project leader should modify the tab, and give some example text that illustrates how to create an actual project.
 
 
 
It would also be ideal if the sample text was translated into different languages.
 
  
 
=Project About=
 
=Project About=
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
tbd
<span style="color:#ff0000">
 
This page is where you need to place your legacy project template page if your project was created before October 2013. To edit this page you will need to edit your project information template. You can typically find this page by following this address and substituting your project name where it says "OWASP_Example_Project". When in doubt, ask the OWASP Projects Manager.
 
Example template page: https://www.owasp.org/index.php/Projects/OWASP_Example_Project
 
</span>
 
  
 
{{:Projects/OWASP_Example_Project_About_Page}}  
 
{{:Projects/OWASP_Example_Project_About_Page}}  

Revision as of 17:35, 14 July 2016

OWASP Project Header.jpg

OWASP DeepViolet TSL/SSL Scanner Code Project

DeepViolet is a TLS/SSL scanning library/tool written in Java. Use DeepViolet from the command line in your own *nix or Windows scripts. Alternatively, use the graphical user interface to scan HTTPS web servers from your desktop or include the DeepViolet API to include TLS/SSL scanning in your applications. Check server certificate trust chains, revocation status, check certificates for pending expiration, weak signing algorithms and more.

Description

Great free and commercial products exist in the TLS/SSL scanning space. The reason to build a new TLS/SSL scanning tool was, 1) learn more about TLS/SSL protocols, crypto, and trust management. In fact, learn everything there is to know about the brief moment a web browser connects to a secure web server, 2) develop a tool in Java.

Project requirements: Java SE 8. Tested on OS X 10.11.5 El Capitan and Windows 10. GitHub includes Travis CI Build Badge to provide code compile confidence.

Licensing

This library is free software: you can redistribute it and/or modify it under the terms of the Apache License, Version 2.0. You can copy, distribute and transmit the work, and you can adapt it, and use it commercially, but all provided that you attribute the work and if you alter, transform, or build upon this work, you may distribute the resulting work only under the same or similar license to this one.

Project Resources

Source Code

Release Binaries

Issue Tracker

Slide Presentation tbd

Video tbd

Project Leader(s)

email:Milton Smith twitter:@spoofzu

Related Projects

tbd

Classifications

Project Type Files CODE.jpg
Incubator Project Owasp-builders-small.png
Owasp-defenders-small.png
Affero General Public License 3.0


News and Events

  • [17 May 2016] Beta4 Release Candidate is available for download. See release notes for detail.

Following are various frequently asked questions.

How can I participate in your project?

All you have to do is make the Project Leader's aware of your available time to contribute to the project. It is also important to let the Leader's know how you would like to contribute and pitch in to help the project meet it's goals and milestones. There are many different ways you can contribute to an OWASP Project, but communication with the leads is key.

If I am not a programmer can I participate in your project?

Yes, you can certainly participate in the project if you are not a programmer or technical. The project needs different skills and expertise and different times during its development. Currently, we are looking for researchers, writers, graphic designers, and a project administrator.

tbd

Volunteers

tbd

Roadmap

This project is already operational and includes a number of powerful features. Deliverables include, 1) binary to perform TLS/SSL scanning from command line, 2) binary to perform TLS/SSL scanning from desktop, 3) binary API interfaces to include TLS/SSL scanning in other Java projects. Project includes basic documentation.

Project requirements: Java SE 8. Tested on OS X 10.11.5 El Capitan and Windows 10. GitHub includes Travis CI Build Badge to provide code compile confidence.


Getting Involved

Involvement in the development and promotion of Code Project Template is actively encouraged! You do not have to be a security expert or a programmer to contribute. Some of the ways you can help are as follows:

Coding

We could implement some of the later items on the roadmap sooner if someone wanted to help out with unit or automated regression tests

Localization

Are you fluent in another language? Can you help translate the text strings in the Code Project Template into that language?

Testing

Do you have a flair for finding bugs in software? We want to product a high quality product, so any help with Quality Assurance would be greatly appreciated. Let us know if you can offer your help.

Feedback

Please send your comments to the project leader(s) or post it as a project issue.

tbd


PROJECT INFO
What does this OWASP project offer you?
RELEASE(S) INFO
What releases are available for this project?
what is this project?
Name: N/A
Purpose: N/A
License: N/A
who is working on this project?
Project Leader(s): N/A
how can you learn more?
Project Pamphlet: Not Yet Created
Project Presentation:
Mailing list: N/A
Project Roadmap: Not Yet Created
Key Contacts
  • Contact the GPC to contribute to this project
  • Contact the GPC to review or sponsor this project
current release
pending
last reviewed release
pending


other releases