|
|
| (15 intermediate revisions by the same user not shown) |
| Line 3: |
Line 3: |
| | {| 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>
| |
| − | ==Project About==
| |
| − | <span style="color:#ff0000">
| |
| − | {{:Template:Project About
| |
| − | |leader_name1=Fatih Çelik
| |
| − | }}
| |
| − |
| |
| − |
| |
| − | ==OWASP Code Project Template==
| |
| − | <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.
| |
| | | | |
| | ==Description== | | ==Description== |
| − | <span style="color:#ff0000">
| + | Vulnerable-Web-Application is a website that is prepared for people who are interested in web penetration and who want to have information about this subject or to be working. In fact, the website is quite simple to install and use. |
| − | 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 Tool 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.
| + | Vulnerable-Web-Application categorically includes Command Execution, File Inclusion, File Upload, SQL and XSS. For database-requiring categories, it creates a database under localhost with one button during setup. In case of corrupted or changed databases, you can create a database again. |
| − | | |
| − | 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 Tool Project Template makes it easier for Project Leaders to create effective security projects and hence helps promote security.
| |
| − | | |
| − | Contextual custom dictionary builder with character substitution and word variations for pen-testers
| |
| | | | |
| | + | [https://github.com/OWASP/Vulnerable-Web-Application Vulnerable Web Application Project Repository] |
| | ==Licensing== | | ==Licensing== |
| − | <span style="color:#ff0000">
| + | [https://www.gnu.org/licenses/gpl-3.0.html GPL] |
| − | 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)}.
| + | The "General Public License" protects users' four essential freedoms, among other things by requiring someone who distributes software derived from yours to also publish the source code for the modifications. Anyone can charge money for distributing copies of the software, but cannot prevent its recipients from redistributing it for free. The GPL allows the copyright holders to distribute the software under additional licenses, too, which can be a way to make it proprietary-friendly. |
| | | | |
| − | ==Roadmap== | + | == How to Contribute == |
| − | <span style="color:#ff0000">
| |
| − | 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
| + | *Solve the challenges in the [https://github.com/OWASP/Vulnerable-Web-Application Vulnerable Web Application Project] |
| − | <strong>
| + | *Choose a category or create new category (CSRF,XML Entity etc.) |
| − | * Internationalization Support | + | *Create the challenge under the choosen category |
| − | * Additional Unit Tests | + | *Submit your work |
| − | * Automated Regression tests | |
| − | </strong>
| |
| | | | |
| − | ==Getting Involved==
| + | | style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" valign="top" | |
| − | <span style="color:#ff0000">
| |
| − | 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:
| |
| | | | |
| − | | valign="top" style="padding-left:25px;width:200px;border-right: 1px dotted gray;padding-right:25px;" |
| + | == Supporters == |
| | | | |
| − | == Project Resources ==
| + | [https://github.com/hummingbirdscyber/ Hummingbirds Cyber Security Community] |
| − | <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 Installation Package]
| + | == Project Leader == |
| − | | + | [mailto:fcelik.ft@gmail.com Fatih Çelik] |
| − | [https://github.com/SamanthaGroves Source Code]
| |
| − | | |
| − | [https://github.com/SamanthaGroves What's New (Revision History)] | |
| − | | |
| − | [https://github.com/SamanthaGroves Documentation]
| |
| | | | |
| − | [https://github.com/SamanthaGroves Wiki Home Page] | + | [https://www.linkedin.com/in/fatih-%C3%A7elik-475560150/ Linkedin] |
| | + | [https://github.com/fatihhcelik Github] |
| | | | |
| − | [https://github.com/SamanthaGroves Issue Tracker] | + | == Core Team == |
| | + | [https://github.com/OguzTozkoparan Mehmet Oğuz Tozkoparan] |
| | | | |
| − | [https://github.com/SamanthaGroves Slide Presentation] | + | [https://github.com/ofsenyayla Ömer Faruk Şenyayla] |
| | | | |
| − | [https://github.com/SamanthaGroves Video] | + | [https://github.com/RamazanEmreErkan Ramazan Emre Erkan] |
| | | | |
| − | == Project Leader ==
| + | [https://github.com/ufuksungu Ufuk Süngü] |
| − | [mailto:fcelik.ft@gmail.com Fatih Çelik] | |
| | | | |
| − | == Related Projects ==
| |
| − | <span style="color:#ff0000">
| |
| − | This is where you can link to other OWASP Projects that are similar to yours.
| |
| − | </span>
| |
| − | * [[OWASP_Tool_Project_Template]]
| |
| − | * [[OWASP_Documentation_Project_Template]]
| |
| | | | |
| | ==Classifications== | | ==Classifications== |
