Opened 12 years ago

Last modified 8 years ago

#826 closed defect (Implemented)

tor-resolve can't adapt to SocksPort change

Reported by: solrex Owned by:
Priority: Low Milestone:
Component: Core Tor/Tor Version:
Severity: Keywords:
Cc: solrex, arma, nickm Actual Points:
Parent ID: Points:
Reviewer: Sponsor:


OS: Ubuntu 8.04
TOR Version:

If the listening socks port changes in /etc/tor/torrc and /etc/tor/tor-tsocks.conf, i.e:

$ diff -ruN torrc torrc.bak
--- torrc.bak 2008-09-27 09:37:47.000000000 +0800
+++ torrc 2008-09-27 09:39:48.000000000 +0800
@@ -18,1 +18,1 @@
-SocksPort 9050 # what port to open for local application connections
+SocksPort 9051 # what port to open for local application connections

$ diff -ruN tor-tsocks.conf.bak tor-tsocks.conf
--- tor-tsocks.conf.bak 2008-09-27 09:37:59.000000000 +0800
+++ tor-tsocks.conf 2008-09-27 09:40:53.000000000 +0800
@@ -7,1 +7,1 @@
-server_port = 9050
+server_port = 9051

tor-resolve will not work. Report this error:

$ tor-resolve
Sep 27 09:46:41.704 [err] Error while connecting to SOCKS host: Connection refused

It seems tor-resolve does not read the configure files in /etc/tor. If I restore configure files to default, everything works OK.

[Automatically added by flyspray2trac: Operating System: Other Linux]

Child Tickets

Change History (5)

comment:1 Changed 12 years ago by arma

tor-resolve doesn't know how to read the torrc file. That would make
the program way more complex.

Take a look at 'man tor-resolve':

tor-resolve [-45] [-v] [-x] hostname [sockshost[:socksport]]

So it looks like you can specify localhost:9051 at the end of the tor-resolve
command line, and it will do what you want.

Would you rather have a "-p 9051" option?

comment:2 Changed 12 years ago by solrex

Thank you. It works. I missed the last options in manual.

Yeah. A "-p 9051" is easier to type.

comment:3 Changed 12 years ago by nickm

Implemented in r17002.

comment:4 Changed 12 years ago by nickm

flyspray2trac: bug closed.

comment:5 Changed 8 years ago by nickm

Component: Tor ClientTor
Note: See TracTickets for help on using tickets.