[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:  TorBrowserTeam201702       |  Actual Points:
Parent ID:                             |         Points:
 Reviewer:                             |        Sponsor:  Sponsor4
---------------------------------------+--------------------------------
Changes (by mcs):

 * status:  needs_review => needs_revision
 * keywords:  TorBrowserTeam201702R => TorBrowserTeam201702


Comment:

 Replying to [comment:33 gk]:
 > Hmm. What about stable users once they get the fix in this bug? Aren't
 they potentially affected as well?

 The versions of Tor Launcher that have shipped on our stable channel have
 never set SocksPort or ControlPort from code, so the likelihood that there
 will be a problem is much lower than for alpha channel users. But you are
 right: if someone has added additional SocksPort or ControlPort lines to
 their torrc, a conflict will occur.

 With some reluctance, Kathy and I believe the best thing to do is for Tor
 Launcher to perform a one-time "fixup" of the user's torrc file. We will
 write code to remove any ControlPort and SocksPort lines that match what
 Tor Launcher will automatically configure via args when it starts tor. We
 will prepare a revised patch soon so we can think about including it in
 the next alpha.

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