[tor-bugs] #22546 [Applications/Tor Browser]: SocksListenAddress error Tor browser 7.0

Tor Bug Tracker & Wiki blackhole at torproject.org
Thu Jun 8 22:01:46 UTC 2017


#22546: SocksListenAddress error Tor browser 7.0
--------------------------------------+-----------------------------------
 Reporter:  torlongtimeuser           |          Owner:  tbb-team
     Type:  defect                    |         Status:  needs_information
 Priority:  Medium                    |      Milestone:
Component:  Applications/Tor Browser  |        Version:
 Severity:  Normal                    |     Resolution:
 Keywords:                            |  Actual Points:
Parent ID:                            |         Points:
 Reviewer:                            |        Sponsor:
--------------------------------------+-----------------------------------
Changes (by brade):

 * status:  new => needs_information


Comment:

 I don't believe this is a bug. It is caused by a change in how SocksPort
 configuration is handled in Tor Browser 7.0. I am sorry we did not
 publicize this very well.

 When I add `SocksListenAddress 0.0.0.0:9150` to my torrc I see this error
 alert:
  "Tor exited during startup.  This might be due to an error in your torrc
 file, a bug in Tor or another program on your system, or faulty hardware.
 Until you fix the underlying problem and restart Tor, Tor Browser will not
 start."

 On the console I see the following messages from tor:
  [warn] The SocksListenAddress option is deprecated, and will most likely
 be removed in a future version of Tor. Use SocksPort instead. (If you
 think this is a mistake, please let us know!)
  [warn] SocksListenAddress can only be used with a single SocksPort with
 value "auto" or 1-65535 and no options set.
  [warn] Failed to parse/validate config: Invalid
 SocksPort/SocksListenAddress configuration
  [err] Reading config failed--see warnings above.

 In Tor Browser 7.0, Tor Launcher passes an arg to tor (via argv) that
 looks like this:
   +__SocksPort 127.0.0.1:9150
 This means that the `SocksListenAddress` line that you added conflicts
 with the configuration that Tor Launcher is passing to tor.

 Do you think you need to use `SocksListenAddress`? Note that this config
 directive has been deprecated. You can add more SocksPort lines to your
 torrc to have tor listen on more interfaces and/or ports.

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


More information about the tor-bugs mailing list