Consider binding to localhost by default

I think users might be surprised if their box starts running an open proxy by nature of running mitmproxy. I propose changing the default to act like mitmproxy -b 127.0.0.1 instead.

[KOLANICH]

Soon after I have started mitmproxy I found it was connected by differrent external ip addresses. I want to tell you that mitmproxy is just a free open source replacement (and it still misses lots of features) for Telerik Fiddler (which is proprietary) and Fiddler by default disallows remote connections to protect their users. Why the f*ck do you do in the other way? Why the f*ck don’t you send the headers by default with information about the remote hosts using the proxy by default to deter abuse? Are you somehow related to the ones who scan the networks for open mitmproxies to use them?

[javabrett]

I’m usually all-for conservative approaches when it comes to security, but in this case I think it is reasonable that, in deliberately starting a known proxy-server including the word proxy in its binary name, you should be willing to accept that by-default this will install an open-proxy server. Hopefully it is sufficient that there is already a mechanism to restrict the address/adapter binding if desired.

My 2c worth.