I did some preliminary testing for my mitmproxy SlackBuild. All dependencies are uploaded to SBo except for urwid. mitmproxy and urwid are pending upload. If anyone is interested to help test mitmproxy here are the relevant SlackBuilds.
You can install the dependencies (except urwid, which is manual installation) like so:
Code:
sbopkg -i "netlib pyasn1 tornado python-configargparse pyperclip blinker pyparsing html2text construct six lxml python-pillow click pysetuptools"
To test you will need a gateway and two other computers. I used virtual machines. One computer needs to have mitmproxy and dependencies installed, we will call this the attacker. The second computer needs to have a working web browser that supports SSL, which is the victim machine. The easiest way to do a man-in-the-middle attack on the attacking machine is to install the dsniff package from SBo and use the arpspoof command. On a minimal installation of Slackware you can use "links" to test on the victim machine.
The -r switch will poison both directions automatically so there is no need to issue a second arpspoof command. I had the -r switch patched into arpspoof sometime in November.
Code:
sudo arpspoof -t <gateway_ip> <target_ip> -r
I have only tested mitmproxy in transparent host mode. The command for that is:
Code:
sudo mitmproxy -T --host
On the victim machine, fire up a web browser, log into a site with SSL, watch the requests on the screen fly by in the mitmproxy UI.
Here is a blog post (not written by me) discussing how to use mitmproxy with a mobile device.
You can post back here or in the
GitHub ticket I created for mitmproxy if there are any difficulties. (Preferably on the GitHub ticket.)