[tor-bugs] #20761 [Applications/Tor Launcher]: Tor Browser 6.5a4 is ignoring additional SocksPorts

[Tor Bug Tracker & Wiki]

#20761: Tor Browser 6.5a4 is ignoring additional SocksPorts
---------------------------------------+--------------------------------
 Reporter:  gk                         |          Owner:  mcs
     Type:  defect                     |         Status:  needs_revision
 Priority:  Medium                     |      Milestone:
Component:  Applications/Tor Launcher  |        Version:
 Severity:  Normal                     |     Resolution:
 Keywords:  TorBrowserTeam201705       |  Actual Points:
Parent ID:                             |         Points:
 Reviewer:                             |        Sponsor:  Sponsor4
---------------------------------------+--------------------------------

Comment (by mcs):

 Replying to [comment:40 gk]:
 > What worries me more is how we would deploy the patch and related ones
 in the stable series. The thing is that probably a lot of users on macOS
 and Linux who are using e.g. TorBirdy have it configured to point to Tor
 Browser. And just switching to unix domain sockets in it is breaking
 things. I am actually not sure if doing that is worth it as we are not
 really enhancing security by ripping AF_INET related code out or enforcing
 it by sandboxing means in the stable series. Breaking a bunch of setups
 for no real enhancement seems not to be the way to go IMO.

 You make a good point that, given the lack of sandboxing in the stable
 series, it does not make sense to break things that previously worked
 (such as TorBirdy finding a SOCKS listener on TCP port 9150). Maybe we
 should ship our stable releases with
 `extensions.torlauncher.control_port_use_ipc = false` and
 `extensions.torlauncher.socks_port_use_ipc = false`.
 >

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/20761#comment:45>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online