Skip to content

GitLab

Trac
Trac

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

Closed (moved)
Opened by Roger Dingledine@arma

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

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.

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information