[tor-bugs] #22641 [Core Tor/Tor]: If you setconf socksport=1000, it returns 553 error but then it sets it anyway, and getconf socksport still returns 9050 even though that's closed

Tor Bug Tracker & Wiki blackhole at torproject.org
Sat Jun 17 19:58:33 UTC 2017


#22641: If you setconf socksport=1000, it returns 553 error but then it sets it
anyway, and getconf socksport still returns 9050 even though that's closed
--------------------------+------------------------------------
 Reporter:  arma          |          Owner:
     Type:  defect        |         Status:  new
 Priority:  Medium        |      Milestone:  Tor: 0.3.2.x-final
Component:  Core Tor/Tor  |        Version:
 Severity:  Normal        |     Resolution:
 Keywords:                |  Actual Points:
Parent ID:                |         Points:
 Reviewer:                |        Sponsor:
--------------------------+------------------------------------

Comment (by arma):

 When you start your Tor with socksport 1000, it gives you
 {{{
 Jun 17 15:55:04.903 [notice] Opening Socks listener on 127.0.0.1:1000
 Jun 17 15:55:04.903 [warn] Could not bind to 127.0.0.1:1000: Permission
 denied
 Jun 17 15:55:04.904 [warn] Failed to parse/validate config: Failed to bind
 one of the listener ports.
 Jun 17 15:55:04.904 [err] Reading config failed--see warnings above.
 }}}
 I.e. it refuses to start.

 So maybe the fix here is that we should actually back out the setconf
 attempt? Rather than saying we backed it out but then not actually doing
 so?

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


More information about the tor-bugs mailing list