Skip to content
andresriancho edited this page Nov 28, 2013 · 11 revisions

Welcome to the w3af wiki! Please view the index for this wiki in order to get a complete list of all available content.

The w3af project has grown substantially over the years and when migrating from the SVN server to GIT we decided to create different repositories to reduce the time required by users to get w3af by cloning the main repository and also to organize the development. These are all our repositories:

  • w3af the web application scanner source code
  • w3af-packages packages for installing w3af in different operating systems
  • w3af-webui a web UI for w3af
  • w3af-moth a set of vulnerable scripts to test w3af
  • w3af-qa QA related stuff
  • w3af-misc Misc files, performance tests, etc.

Report a bug

Reporting bugs in such a way that they are useful to the developers is an art which not many practice. Master it by following these simple steps:

  • Describe the minimal number of steps you need to take to reproduce the bug
  • Include your operating system and Python version (python --version)
  • If you've got a python traceback please include it. Tracebacks start with: Traceback (most recent call last):
  • If there is no traceback, please:
    • Enable the output.text_file plugin and enable it's verbose mode
    • Make sure you take note of the log file location
    • Run the scan which triggers the bug, and analyze the output file. Try to find errors, warnings and tracebacks. Include them in your bug report. If you want, create a gist with the whole log file and add a link to it in your bug report.
    • Keep in mind that the log file contains more information than the console or GUI interfaces, so even if they are frozen or seem inactive new log entries might appear on the log. Performing a tail -f path/to/logfile.txt while running the scan is a good idea.

Bugs are reported by submitting an issue to the github tracker.

Shortcuts