|
@@ -860,7 +860,7 @@ The following options are useful only for clients (that is, if
|
|
|
the same circuit. Currently, two addresses are "too close" if they lie in
|
|
|
the same /16 range. (Default: 1)
|
|
|
|
|
|
-**SOCKSPort** \['address':]__port__|**auto** [_isolation flags_]::
|
|
|
+**SOCKSPort** \['address':]__port__|**auto** [_flags_] [_isolation flags_]::
|
|
|
Open this port to listen for connections from SOCKS-speaking
|
|
|
applications. Set this to 0 if you don't want to allow application
|
|
|
connections via SOCKS. Set it to "auto" to have Tor pick a port for
|
|
@@ -894,6 +894,18 @@ The following options are useful only for clients (that is, if
|
|
|
port with the same session group. (By default, streams received
|
|
|
on different SOCKSPorts, TransPorts, etc are always isolated from one
|
|
|
another. This option overrides that behavior.)
|
|
|
++
|
|
|
+ Other recognized _flags_ for a SOCKSPort are:
|
|
|
+ **PreferSOCKSNoAuth**;;
|
|
|
+ Ordinarily, when an application offers both "username/password
|
|
|
+ authentication" and "no authentication" to Tor via SOCKS5, Tor
|
|
|
+ selects username/password authentication so that IsolateSOCKSAuth can
|
|
|
+ work. This can confuse some applications, if they offer a
|
|
|
+ username/password combination then get confused when asked for
|
|
|
+ one. You can disable this behavior, so that Tor will select "No
|
|
|
+ authentication" when IsolateSOCKSAuth is disabled, or when this
|
|
|
+ option is set.
|
|
|
+
|
|
|
|
|
|
**SOCKSListenAddress** __IP__[:__PORT__]::
|
|
|
Bind to this address to listen for connections from Socks-speaking
|