Version 0.2.3

This commit is contained in:
Rob Glew 2016-01-27 16:51:40 -06:00
parent 28b7b7e8ff
commit d805eabeec
15 changed files with 559 additions and 127 deletions

View file

@ -59,9 +59,9 @@ author = u'Rob Glew'
# built documents.
#
# The short X.Y version.
version = u'0.2.2'
version = u'0.2.3'
# The full version, including alpha/beta/rc tags.
release = u'0.2.2'
release = version
# The language for content autogenerated by Sphinx. Refer to documentation
# for a list of supported languages.

View file

@ -33,8 +33,6 @@ Anyways, here's some ideas for things you could implement:
Find a library to perform some kind of check for weak ciphers, etc on a host and print out any issues that are found.
* Add a SQLMap button
Make it easy to pass a request to SQLMap to check for SQLi. Make sure you can configure which fields you do/don't want tested and by default just give either "yes it looks like SQLi" or "no it doesn't look like SQLi"
* Decoder functionality
Add some commands for encoding/decoding text. If you go after this, let me know because I'm probably going to be pretty picky about how this is implemented. You'll have to do better than just a ``base64_decode <text>`` command.
* Additional macro templates
Write some commands for generating additional types of macros. For example let people generate an intercepting macro that does search/replace or modifies a header. Save as much typing as possible for common actions.
* Show requests/responses real-time as they go through the proxy