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 ZSC Tool Project"
Ali Razmjoo (talk | contribs) |
|||
| Line 144: | Line 144: | ||
'''Note''': Software installation directory is "'''/usr/share/owasp-zsc'''" | '''Note''': Software installation directory is "'''/usr/share/owasp-zsc'''" | ||
| + | = 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 Tool Project Template | ||
| + | * Get other people to review the Tool Project Template and provide feedback | ||
| + | * Incorporate feedback into changes in the Tool Project Template | ||
| + | * Finalize the Tool 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> | ||
= Developers = | = Developers = | ||
Revision as of 20:22, 5 August 2015
OWASP ZSC Tool ProjectWhat is OWASP ZSC ?OWASP ZSC is an open source software in python language which lets you generate customized shellcodes for listed operation systems. This software could be run on Linux under python 2.7.x.
DescriptionUsage of shellcodesShellcodesare small codes in assembly which could be use as the payload in software exploiting. Other usages are in malwares, bypassing antiviruses, obfuscated codes and etc. Why use OWASP ZSC ?According to other shellcode generators same as metasploit tools and etc, OWASP ZSC using new encodes and methods which antiviruses won't detect. OWASP ZSC encoderes are able to generate shellcodes with random encodes and that's lets you to get thousands new dynamic shellcodes with same job in just a second,that means you will not get a same code if you use random encodes with same commands, And that make OWASP ZSC one of the bests! otherwise it's gonna generate shellcodes for many operation systems in next versions. LicensingGNU GENERAL PUBLIC LICENSE , Version 3, 29 June 2007Copyright (C) 2007 Free Software Foundation, Inc. http://fsf.org/ Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed. Click to see the full license
The OWASP Security Principles are licensed under the http://creativecommons.org/licenses/by-sa/3.0/ Creative Commons Attribution-ShareAlike 3.0 license], so 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 LeaderLinksShellcode GeneratingWith using OWASP ZSC you would be able to generate any customized Shellcode in your mind including encodes,and Disassembly code in few seconds. Be an OWASP ZSC developerLast Tricks in Home
|
Quick DownloadThe home of the OWASP Security Principles is on GitHub. You are encourged to fork, edit and push your changes back to the project through git or edit the project directly on github. However, if you like you may also download the master repository from the following links: News and Events
DocsClassifications
| |||||||
