Not to be confused with mitm-proxy[1], which is java-based.
For diagnostics I'd prefer something like Paros[2], Burp[3] or WebScarab[4], which has a graphical interface, but this one seems to offer a quite nice scripting API which I'll have to take a closer look at.
I have used stanford's ssl-mitm, Paros and WebScarab.
The one being shown here is better than all of them, actually.
The textual interface is actually a curses-based interface that lets you do stuff as you would normally do in paros, such as capture a request or edit a request and replay it. So it is not just like you're watching logs. You can take many kinds of actions from within that text interface, and very quiclky. The scripting API is also very good.
Burp is fantastic. The free version is great, the paid version (which is very cheap) is even better. All our developers use burp to catch traffic between their development simulators and the testbed for debugging.
There's a bunch of these proxies out there, and they all provide something different, but if you're just looking to inspect the HTTPS request, I'd also recommend the excellent Charles Web Proxy - http://www.charlesproxy.com/ - I bought a copy years ago, and it's been invaluable.
Fortinet has a similar feature for the Fortigates. You can have the SSL cert (ex: secure.yourcompany.com) be presented from an IP bound to the firewall and be able to read all communications between the client and server. I'm not sure if the same applies to a certificate you don't own (ex: mail.google.com) for the same purpose.
this handles all the certificate work on its own and auto generates and stores certificates in ~/.mitmproxy or something similar so you can quickly email it to your iDevice. although it is a little eerie to see my bank password in "plain-text", its fun to look at how other app makers send and receive data.
another great use is for diagnosing mobile applications (including ones you did not write) without needing to sniff wpa2 traffic. also, even as just a startup of 15 people, we use wpa2 enterprise to avoid such simple wireshark usage.
For diagnostics I'd prefer something like Paros[2], Burp[3] or WebScarab[4], which has a graphical interface, but this one seems to offer a quite nice scripting API which I'll have to take a closer look at.
[1] http://crypto.stanford.edu/ssl-mitm/
[2] http://www.parosproxy.org/
[3] http://www.portswigger.net/burp/proxy.html
[4] https://www.owasp.org/index.php/Category:OWASP_WebScarab_Pro...