[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:55:32 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        |   Keywords:
Actual Points:                |  Parent ID:
       Points:                |   Reviewer:
      Sponsor:                |
------------------------------+--------------------------------
 Run your Tor not as root, then connect to your control port and do
 {{{setconf socksport=1000}}}. Tor will reply with
 {{{
 553 Unable to set option: Failed to bind one of the listener ports.
 }}}
 and it will log
 {{{
 Jun 17 15:48:09.939 [notice] Opening Socks listener on 127.0.0.1:1000
 Jun 17 15:48:09.939 [warn] Could not bind to 127.0.0.1:1000: Permission
 denied
 Jun 17 15:48:09.939 [notice] Closing no-longer-configured Socks listener
 on 127.0.0.1:9050
 Jun 17 15:48:09.939 [warn] Controller gave us config lines that didn't
 validate: Failed to bind one of the listener ports.
 }}}

 So it closed my socksport 9050, and then it was unhappy with the 1000.

 Soon, I get another log line:
 {{{
 Jun 17 15:48:33.592 [notice] Opening Socks listener on 127.0.0.1:1000
 Jun 17 15:48:33.592 [warn] Could not bind to 127.0.0.1:1000: Permission
 denied
 Jun 17 15:48:33.592 [notice] Closing no-longer-configured Socks listener
 on 127.0.0.1:9050
 }}}

 Looks like Tor tries periodically to open it, in hopes that it'll work
 this time.

 Bug one is that Tor shouldn't reply to the setconf with an error but then
 secretly honor it anyway.

 And woah, check this out:
 {{{
 getconf socksport
 250 SocksPort=9050
 }}}

 So bug number two is that it looks like Tor has been unsynchronized about
 what its SocksPort actually is.

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


More information about the tor-bugs mailing list