List view
This will help us just upload to readthedocs, and be done with this silly documentation generation issue.
No due dateThis will allow for easier querying, as well as viewing the data raw, without the need for special wrappers for the data we use. I also don't see this causing a performance issue, although who knows.
No due dateJust to track all the enhancements.
No due date•0/3 issues closedJust a milestone to fix the current bug reports, so I have some progress to work off of.
No due date•2/7 issues closedEventually I'd like to build an executable to fuzz and make sure I get the proper stack-traces, etc from it, and build it up to the point where I can also generate epydocs every night, that way fuzzing.org can just point to those up to date docs.
No due date•0/1 issues closedAdd the ability (and documentation) to get Sulley running on an iPhone, so we can really break the world!
No due dateSwitch from PyDBG to VDB, as it's cross-platform, and gets rid of the need for two process_monitor scripts (as well as the round-about way to obtain a stacktrace on unix), and should be more stable for getting this running on any platform necessary.
No due date•0/2 issues closedFile fuzzing should be simplified and elegant, the proposed changes were a bit hacky.
No due dateThe fixes pushed in by Nibbler only operate on sessions.py, although sulley talks in other places.
No due date•0/1 issues closedThe first step in getting Sulley talking to Scapy, and having layer 2 fuzzing working on Windows.
No due dateI'm thinking maybe a cherrypy/flask project with a nice AJAX interface to fetch updates and pause fuzzing. Perhaps even a job queue? And definitely having the fuzz test cases available on hand so when something breaks it's one click to see what triggered your bug.
No due date•0/4 issues closedEventually I'd like to take the libdnet stuff and extend it to automatically do things like checksumming, all of which I have planned can be done very easily through Scapy.
No due date