Main
← Older revision
Revision as of 01:11, 29 August 2016
(5 intermediate revisions by the same user not shown)
Line 7:
Line 7:
==OWASP OMTG Hacking Playground Tool Project ==
==OWASP OMTG Hacking Playground Tool Project ==
−
<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 OMTG hacking playground consists of a vulnerable Android App that maps to the different test cases in the OWASP Mobile Testing Guide. An iOS will be available soon.
The OMTG hacking playground consists of a vulnerable Android App that maps to the different test cases in the OWASP Mobile Testing Guide. An iOS will be available soon.
Line 33:
Line 30:
</span>
</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)}.
+
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.
| 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;" |
Line 70:
Line 67:
== News and Events ==
== 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.
+
* [
Sep 2016
]
Talk at Null Singapore about OMTG
and
Hacking Playground
−
</span>
+
* [
July 2016
]
First Android Version
available
via GitHub
.
−
* [
12 Feb 2013
]
Support for Spanish is now available with this release.
+
−
* [11 Jan 2014] The 1.0 stable version has been released! Thanks everyone for your feedback
and
code fixes that made this happen!
+
−
* [
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.-->
−
<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 97:
Line 84:
==Contributors==
==Contributors==
−
<!-- Instructions are in RED and should be removed from your document by deleting the text with the span tags.-->
+
=
=Volunteers==
−
<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 Tool Project Template 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].
+
Sven Schleier
−
+
Ryan Teoh
−
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 Tool Project Template
+
−
* '''YOUR NAME BELONGS HERE AND YOU SHOULD REMOVE THE PRIOR 3 NAMES'''
+
= Road Map and Getting Involved =
= Road Map and Getting Involved =
Line 154:
Line 131:
<li>What features would you like to see prioritized on the roadmap?</li>
<li>What features would you like to see prioritized on the roadmap?</li>
</ul>
</ul>
−
−
=Minimum Viable Product=
−
<!-- 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 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 Tool 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=