In tor-resolve, when the Tor client to use is specified by <hostname>:<port>, actuall...

svn:r18833

diff --git a/ChangeLog b/ChangeLog
index f37d1368e55d302a212246eba385e64b11a046c6..91ab990814c0bda665bfaad7dbfd59653a5b6f4a 100644 (file)
--- a/ChangeLog
+++ b/ChangeLog
@@ -3,6 +3,9 @@ Changes in version 0.2.1.14-??? - 2009-03-??
     - Avoid trying to print raw memory to the logs when we decide to
       give up on downloading a given relay descriptor. Bugfix on
       0.2.1.9-alpha.
+    - In tor-resolve, when the Tor client to use is specified by
+      <hostname>:<port>, actually use the specified port rather than
+      defaulting to 9050. Bugfix on 0.2.1.6-alpha.
 
 
 Changes in version 0.2.1.13-alpha - 2009-03-09

diff --git a/src/tools/tor-resolve.c b/src/tools/tor-resolve.c
index 100c8107a44a43272ab350f4e4b464413568305d..6ea2dc2352a7f2509ea6bc57d70571ae0c230f6b 100644 (file)
--- a/src/tools/tor-resolve.c
+++ b/src/tools/tor-resolve.c
@@ -388,7 +388,7 @@ main(int argc, char **argv)
                (int)socksport, (int)port_option);
     } else if (port_option) {
       socksport = port_option;
-    } else {
+    } else if (!socksport) {
       log_debug(LD_CONFIG, "defaulting to port 9050");
       socksport = 9050;
     }