Tor Launcher: Ensure we always have a Tor on 127.0.0.1:9050
I believe that until we ship Vidalia bundle again, we should ensure that TBB on Mac OS X and Windows will provide a Tor SOCKS proxy on 127.0.0.1:9050 for any additional application that needs a predictable SOCKS proxy.
I propose that the GNU/Linux builds of TBB should only have 127.0.0.1:9150 for SOCKS as the system may provide a Tor SOCKS proxy from system packages on 127.0.0.1:9050.
I believe that the
torrc in the TBB on Mac OS X needs a two line diff and on Windows it should be the same patch.
The patch that seems to ensure that I have both a working Tor on 9050 and 9150 was to patch the torrc like so:
-SocksPort 9150 -SocksListenAddress 127.0.0.1 +SocksPort 127.0.0.1:9050 +SocksPort 127.0.0.1:9150
What needs to be tested to ensure that the next TBB releases can have these changes for Mac OS X and Windows releases?
Without these changes, torsocks and TorBirdy users are currently left out in the cold until we start to ship Vidalia bundles again. There is no ETA for those bundles as far as I understand things - so this is a critical issue for nearly every application that uses Tor except the Tor Browser itself on Windows/Mac OS X.