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

Tor Bug Tracker & Wiki blackhole at torproject.org
Tue Dec 6 19:41:38 UTC 2016


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

Comment (by mcs):

 Given the way tor behaves today and the fact that we don’t have much time
 to change it, Kathy and I have two options to propose:

 Proposal 1 (require users to set prefs to configure additional listeners):
 A. Switch the default values of the use_ipc prefs to false so that TCP
 ports are used by default.
 B. Remove the SocksPort and ControlPort lines from torrc-defaults because
 they are not used.
 C. When configuring listeners, Tor Launcher will use the same method as in
 TB 6.5a5 (command line arguments) except it will also recognize new prefs
 (e.g., extensions.torlauncher.socks_port_extra.1) and pass additional
 command line arguments to enable additional listeners.

 Proposal 2 (allow users to transition from config file to preferences):
 A. Switch the default values of the use_ipc prefs to false so that TCP
 ports are used by default (as in Proposal 1).
 B. If use_ipc is false, Tor Launcher will not configure the listener via
 command line arguments; instead, it will rely on the torrc-default / torrc
 settings like TB 6.0.x does.
 C. If use_ipc is true, the behavior for the will be as in TB 6.5a5 except
 Tor Launcher will recognize new prefs (e.g.,
 `extensions.torlauncher.socks_port_extra.1`) and pass additional command
 line arguments to enable the additional listeners (as in Proposal 1).
 As an exception to “B” above, Kathy and I think it makes sense to use the
 extra prefs even when use_ipc is false if any "port_extra" pref values
 have been added by the user (instead of relying on the config file).

 Proposal 1 is simpler but forces advanced users to change how they
 configure things as soon as they start using TB 6.5. Proposal 2 will be a
 little more complex to implement and maintain, but it has the advantage
 that users who are content to stick with TCP can continue to configure all
 of their ports via the torrc file.

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


More information about the tor-bugs mailing list