OWASP QRLJacker

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. Project About PROJECT INFO What does this OWASP project offer you? RELEASE(S) INFO What releases are available for this project? what is this project? Name: QRLJacker Purpose: N/A License: N/A who is working on this project? Project Leader(s): Mohamed A. Baset how can you learn more? Project Pamphlet: Not Yet Created Project Presentation: Mailing list: N/A Project Roadmap: Not Yet Created Key Contacts Contact Mohamed A. Baset to contribute to this project Contact Mohamed A. Baset to review or sponsor this project current release https://github.com/OWASP/QRLJacking/tree/master/QRLJacker last reviewed release Not Yet Reviewed other releases QRLJacker Exploitation Framework A customizable framework to demonstrate "QRLJacking Attack Vector" and to show how easy it is to hijack services that rely on QR Code Authentication! Licensing A project must be licensed under a community friendly or open source license.  For more information on OWASP recommended licenses, please see 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. This program is free software: you can redistribute it and/or modify it under the terms of the 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)}. Roadmap As of November, 2013, the highest priorities for the next 6 months are: 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 Subsequent Releases will add Internationalization Support Additional Unit Tests Automated Regression tests Getting Involved Involvement in the development and promotion of Tool 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:

Project Resources 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. Installation Package Source Code What's New (Revision History) Documentation Wiki Home Page Issue Tracker Slide Presentation Video Project Leader 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. Mohamed Baset Related Projects This is where you can link to other OWASP Projects that are similar to yours. OWASP_Code_Project_Template OWASP_Documentation_Project_Template Classifications