|
|
| (68 intermediate revisions by 2 users not shown) |
| Line 1: |
Line 1: |
| − | =Main=
| |
| − |
| |
| | <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div> | | <div style="width:100%;height:160px;border:0,margin:0;overflow: hidden;">[[File:OWASP_Project_Header.jpg|link=]]</div> |
| | | | |
| | {| 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;" | | + | | style="border-right: 1px dotted gray;padding-right:25px;" valign="top" | |
| | | | |
| − | <span style="color:#ff0000">
| + | ==OWASP DeepViolet TLS/SSL API Project and Tools== |
| − | 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==
| + | DeepViolet is a TLS/SSL scanning API written in Java. To keep DeepViolet easy to use, identify bugs, reference implementations have been developed that consume the API. If you want to see what DeepViolet can do, use it from the command line in your scripts or use the graphical tool from the comfort of your desktop. Both tools can be used to scan HTTPS web servers to check server certificate trust chains, revocation status, check certificates for pending expiration, weak signing algorithms and much more. |
| − | <span style="color:#ff0000">
| |
| − | This section should include an overview of what the project is, why the project was started, and what security issue is being addressed by the project deliverable. Some readers may be discouraged from looking further at the project if they do not understand the significance of the security concern that is being addressed, so provide enough context so the average reader will continue on with reading the description. You shouldn't assume the reader will understand the objective by providing security terminology, e.g. this project builds cryptographic algorithms, but should also endeavor to explain what they are used for.
| |
| − | </span>
| |
| | | | |
| − | The OWASP Code Template Project is a template designed to help Project Leaders create suitable project pages for OWASP Projects. By following the instructional text in red (and then deleting it) it should be easier to understand what information OWASP and the project users are looking for. And it's easy to get started by simply creating a new project from the appropriate project template.
| + | ==How is DeepViolet Helpful?== |
| | | | |
| − | Code Library Project
| + | Already great tools exist today for TLS/SSL scanning like, [https://www.ssllabs.com/ssltest/index.html, Qualys Labs], [https://observatory.mozilla.org/, Mozilla Observatory], [https://www.openssl.org/, OpenSSL]. Why do I care about DeepViolet? A valid question and one I asked myself. Originally, DeepViolet was written as an educational tool. A tool to learn TLS/SSL protocols and some of the issues around recent attack trends better. The goal was not to develop a TLS/SSL scanner and compete with existing powerful tools. However, it turns out there are few choices for easy to use open source Java TLS/SSL scanning APIs. What better way to learn TLS/SSL and provide other scanning projects with a Java friendly API scanning solution - the DeepViolet project was born. |
| | | | |
| − | ==Description== | + | ==Licensing== |
| − | <span style="color:#ff0000">
| |
| − | 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.
| + | 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. |
| | | | |
| − | 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.
| + | | style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" | |
| | | | |
| − | ==Licensing== | + | == Quick Start == |
| | | | |
| − | Apache 2.0 License (fewest restrictions, even allowing proprietary modi cations and
| + | See project [https://github.com/spoofzu/DeepViolet GitHub home page] |
| − | 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 © by {the Project Leader(s) or OWASP} {Year(s)}.
| + | == Project Resources == |
| | | | |
| − | | valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" | | + | [https://github.com/spoofzu/DeepViolet Code] | [https://github.com/spoofzu/DeepViolet/releases Binaries] | [https://spoofzu.github.io/DeepViolet/ API JavaDocs] |
| | | | |
| − | == Project Resources ==
| + | [https://github.com/spoofzu/DeepViolet/issues Issue Tracker] |
| − | <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/SamanthaGroves Compiled DLLs] | + | [https://github.com/spoofzu/DeepViolet/issues/5 Road Map(Beta 5)] |
| | | | |
| − | [https://github.com/SamanthaGroves Source Code] | + | [https://groups.google.com/forum/#!forum/deepviolet-development DeepViolet Dev Group], ask questions |
| | | | |
| − | [https://github.com/SamanthaGroves Documentation] | + | Twitter: [https://twitter.com/deepvioletapi @DeepVioletAPI] |
| | | | |
| − | [https://github.com/SamanthaGroves Wiki Home Page]
| + | ==Requirements== |
| | | | |
| − | [https://github.com/SamanthaGroves Issue Tracker]
| + | Java SE 8+ |
| | | | |
| − | [https://github.com/SamanthaGroves Slide Presentation]
| + | Tested on OS X and Windows |
| | | | |
| − | [https://github.com/SamanthaGroves Video]
| + | | style="padding-left:25px;width:200px;" valign="top" | |
| | | | |
| − | == Project Leader == | + | == Project Leader(s) == |
| − | <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)
| + | Milton Smith<br /> |
| − | | + | [ https://www.securitycurmudgeon.com/ blog] [https://twitter.com/spoofzu/ twitter] [ mailto:[email protected] email] |
| − | | |
| | | | |
| | == Related Projects == | | == Related Projects == |
| − | <span style="color:#ff0000">
| + | [https://www.owasp.org/index.php/OWASP_Zed_Attack_Proxy_Project OWASP Zed Attack Proxy Project] |
| − | This is where you can link to other OWASP Projects that are similar to yours.
| + | |
| − | </span>
| + | [https://www.owasp.org/index.php/OWASP_Security_Logging_Project OWASP Security Logging Project] |
| | | | |
| − | * [[OWASP_Code_Tool_Template]] | + | == News and Events == |
| − | * [[OWASP_Documentation_Project_Template]] | + | * [24 Jul 2018] SecurityOnline.info: OWASP DeepViolet TLS/SSL API |
| | + | * [Jun 8, 2018] DV at [https://www.blackhat.com/us-18/arsenal/schedule/index.html#deepviolet-ssltls-scanning-api-38-tools-10724 Blackhat 2018 USA] |
| | + | * [Jun 8, 2018] Significant updates to DV and DeepVioletTools code |
| | + | * [27 September 2017] [https://www.elementarydigital.co.uk/the-best-ssl-troubleshooting-tools-to-test-out/ Elementary: The Best SSL Troubleshooting Tools to Test Out] |
| | + | * [1 June 2017] ZAP's HttpsInfo addon leveraging DeepViolet has been released (v9) [http://bit.ly/2r6mmBj More] |
| | + | * [25 May 2017] DeepViolet Beta 5.0.2 available for download, See [https://github.com/spoofzu/DeepViolet/releases/tag/5.0.2 release notes] for detail. |
| | + | * [10 November 2016] SlideShare, [http://www.slideshare.net/MiltonSmith6/owasp-deepviolet-tlsssl-java-api-and-tools BlackHat 2016 EU Slide Deck] |
| | + | * [22 October 2016] Peerlyst, [https://www.peerlyst.com/posts/ssl-tls-session-introspection-deepviolet-cyberpunk SSL TLS Session Introspection: DeepViolet] |
| | + | * [2 September 2016] Improving documentation and [https://github.com/spoofzu/DeepViolet/issues/5 roadmap for Beta5]. |
| | + | * [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. |
| | + | * [22 April 2016] Oracle Blogs, [https://blogs.oracle.com/java-platform-group/entry/javaone_2016_call_for_proposals JavaOne 2016 Call for Proposals] |
| | + | * [6 April 2016] Sans Institute, [https://www.sans.org/reading-room/whitepapers/auditing/defending-weaponization-trust-defense-in-depth-assessment-tls-37145 Defending Against the Weaponization of Trust: Defense in Depth Assessment of TLS] |
| | | | |
| | ==Classifications== | | ==Classifications== |
| Line 81: |
Line 71: |
| | {| width="200" cellpadding="2" | | {| width="200" cellpadding="2" |
| | |- | | |- |
| − | | colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]] | + | | colspan="2" align="center" | [[File:Project_Type_Files_CODE.jpg|link=]] |
| | |- | | |- |
| − | | align="center" valign="top" width="50%" rowspan="2"| [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]] | + | | rowspan="2" width="50%" valign="top" align="center" | [[File:Owasp-incubator-trans-85.png|link=https://www.owasp.org/index.php/OWASP_Project_Stages#tab=Incubator_Projects|Incubator Project]] |
| − | | align="center" valign="top" width="50%"| [[File:Owasp-builders-small.png|link=Builders]] | + | | width="50%" valign="top" align="center" | [[File:Owasp-builders-small.png|link=Builders]] |
| | |- | | |- |
| − | | align="center" valign="top" width="50%"| [[File:Owasp-defenders-small.png|link=Defenders]] | + | | width="50%" valign="top" align="center" | [[File:Owasp-defenders-small.png|link=Defenders]] |
| | |- | | |- |
| − | | colspan="2" align="center" | [[File:Agplv3-155x51.png|link=http://www.gnu.org/licenses/agpl-3.0.html|Affero General Public License 3.0]] | + | | colspan="2" align="center" | |
| | |} | | |} |
| − |
| |
| − | | valign="top" style="padding-left:25px;width:200px;" |
| |
| − |
| |
| − | BUILDER PROJECT
| |
| − |
| |
| − | == News and Events ==
| |
| − | <span style="color:#ff0000">
| |
| − | 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= | + | =Roadmap= |
| − | <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
| |
| − | <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?==
| + | This project is operational and includes a number of powerful features. The roadmap is managed via the projects GitHub site, [https://github.com/spoofzu/DeepViolet/issues DeepViolet Roadmap]. For example, at the time of this writing an issue has been created for Beta5 which is labeled, ''Beta5 Proposed Features/Roadmap''. |
| − | 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?==
| + | ''For information about contributing see DeepViolet's [https://github.com/spoofzu/DeepViolet/wiki/Contributing Contributing page] on GitHub.'' |
| − | 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.
| |
| − | | |
| − | = Acknowledgements =
| |
| − | ==Volunteers==
| |
| − | | |
| − | <!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
| |
| − | <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].
| |
| − | | |
| − | 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==
| |
| − | 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==
| |
| − | Involvement in the development and promotion of <strong>Code Project Template</strong> 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 <strong>Code Project Template</strong> 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 use the [https://lists.owasp.org/mailman/listinfo/OWASP_Code_Project_Template Code Project Template project mailing list] for feedback about:
| |
| − | <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.-->
| |
| − | <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}}
| |
| | | | |
| | + | {{Template:Project About |
| | + | | project_name = DeepViolet |
| | + | | project_description = TLS/SSL scanning tool for the command line, desktop, and API to include in your programs. |
| | + | | project_license = [https://github.com/spoofzu/DeepViolet/blob/master/LICENSE Apache License 2.0] |
| | + | | leader_name1 = Milton Smith |
| | + | |
| | + | | leader_username1 = [https://www.owasp.org/index.php/User:Miltonsmith Miltonsmith] |
| | + | | mailing_list_name =[https://lists.owasp.org/mailman/listinfo/deepviolet https://lists.owasp.org/mailman/listinfo/deepviolet] |
| | + | }} |
| | | | |
| | __NOTOC__ <headertabs /> | | __NOTOC__ <headertabs /> |
| | | | |
| − | [[Category:OWASP Project]] [[Category:OWASP_Builders]] [[Category:OWASP_Defenders]] [[Category:OWASP_Code]] | + | [[Category:OWASP Project]] |
| | + | [[Category:OWASP_Builders]] |
| | + | [[Category:OWASP_Defenders]] |
| | + | [[Category:OWASP_Code]] |
