An interactive TLS-capable intercepting HTTP proxy for penetration testers and software developers.
Go to file
Aldo Cortesi 2af6dcf6f7 Documentation. 2011-03-16 15:50:31 +13:00
doc-src Documentation. 2011-03-16 15:50:31 +13:00
examples First pass of script hooks for mitmdump. 2011-02-18 12:40:45 +13:00
libmproxy Interrupt interception when deleting an intercepting flow. 2011-03-15 17:53:29 +13:00
test Interrupt interception when deleting an intercepting flow. 2011-03-15 17:53:29 +13:00
.gitignore Simple record & playback functionality 2011-02-10 02:59:51 +01:00
CHANGELOG Release mitmproxy 0.2 2010-03-01 17:25:27 +13:00
LICENSE Initial checkin. 2010-02-16 17:09:07 +13:00
MANIFEST.in Initial checkin. 2010-02-16 17:09:07 +13:00
README.mkd Documentation. 2011-03-16 15:27:26 +13:00
mitmdump Unify mitmproxy and mitmdump commandline 2011-03-12 14:30:12 +13:00
mitmproxy Fix a number of small UI infelicities. 2011-03-13 21:16:42 +13:00
setup.py Fix setup.py 2011-02-21 12:04:24 +13:00
todo Documentation. 2011-03-16 15:27:26 +13:00

README.mkd

mitmproxy and mitmdump are SSL-capable, intercepting HTTP proxies.

mitmproxy provides a curses interface that allows traffic to be inspected and edited on the fly.

mitmdump is the command-line companion of mitmproxy - like tcpdump for HTTP.

Capabilities

  • Intercept HTTP requests and responses and modify them on the fly.
  • Save complete HTTP conversations for later replay and analysis.
  • Client replay to replay the client-side of an HTTP conversation.
  • Server replay replays the HTTP responses of a previously recorded server.
  • Make scripted changes to HTTP traffic using a simple Python API.
  • Dummy SSL certificate authority creates interception certificates on the fly.

Download

Releases can be found here: http://corte.si/projects.html

Source is hosted here: http://github.com/cortesi/mitmproxy

Requirements

  • A recent Python interpreter.
  • SSL certificates are generated using openssl
  • The curses interface relies on version 0.9.8 or newer of the urwid library.
  • The test suite uses the pry unit testing library.

You should also make sure that your console environment is set up with the following:

  • EDITOR environment variable to determine the external editor.
  • PAGER environment variable to determine the external pager.
  • Appropriate entries in your mailcap files to determine external viewers for request and response contents.