Opened 6 years ago

Last modified 6 weeks ago

#8228 needs_information enhancement

Tor Launcher: Ensure we always have a Tor on 127.0.0.1:9050

Reported by: ioerror Owned by: brade
Priority: Very High Milestone:
Component: Applications/Tor Launcher Version:
Severity: Normal Keywords: needs-triage
Cc: mikeperry, hack@… Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

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.

Child Tickets

Change History (8)

comment:1 Changed 6 years ago by mikeperry

Test that Torbutton always sets a SOCKS port of 9150 in the following conditions:

  1. Set these values in the torrc *before* ever running the bundle.
  2. Change the "Network Settings" options in vidalia and then restart everything.
  3. Do step 2 a few times with various vidalia pref changes, restarting each time.
  4. If you change the order of the SOCKSPort lines in torrc, does it break?

If 4 gives Torbutton a different SOCKS port, have a look at whatever writes the torrc (I think Vidalia sends the control port command SAVECONF) and make sure the ordering is always preserved. Or ask Nick if it is always preserved.

comment:2 in reply to:  1 Changed 6 years ago by malaparte_

Cc: hack@… added

Replying to mikeperry:

  1. If you change the order of the SOCKSPort lines in torrc, does it break?

If you had more than 2 SocksPort lines? in Vidalia's display of Torrc, it was breaking, see #8304 & associated patch

comment:3 Changed 4 years ago by erinn

Keywords: needs-triage added

comment:4 Changed 4 years ago by erinn

Component: Tor bundles/installationTor Browser
Owner: changed from erinn to tbb-team

comment:5 Changed 3 years ago by vynX

Given that no other web browser is recommendable to average users I run into three use cases not exactly considered here (a) some people have a Tor Router not on localhost, (b) some people have an HTTP proxy in front of Tor (see also #16046), (c) some people have some sites that must be used without Tor or generally want to use torbrowser without Tor. I would want to be able to serve such people Torbrowser even if not being used the default way...

comment:6 Changed 10 months ago by teor

Severity: Normal

Set all open tickets without a severity to "Normal"

comment:7 Changed 6 weeks ago by traumschule

Component: Applications/Tor BrowserApplications/Tor Launcher
Owner: changed from tbb-team to brade
Status: newneeds_information
Summary: Ensure we always have a Tor on 127.0.0.1:9050Tor Launcher: Ensure we always have a Tor on 127.0.0.1:9050

Vidalia has been replaced with Tor Launcher

Is it currently possible on Mac / Windows to set SocksPort twice?

comment:8 in reply to:  7 Changed 6 weeks ago by teor

Replying to traumschule:

Vidalia has been replaced with Tor Launcher

Is it currently possible on Mac / Windows to set SocksPort twice?

Tor can open multiple SocksPorts on any platform.

But if we make Tor Browser open 127.0.0.1:9050 on macOS and Windows, we'll interfere with everyone who runs a separate Tor on that port.

Note: See TracTickets for help on using tickets.