Replace 'SOCKSPort' with 'SocksPort'
When applying changes from proposal 171 Nick renamed SocksPort to SOCKSPort, and SocksListenAddress to SOCKSListenAddress... https://gitweb.torproject.org/tor.git/commit/?id=891ccd3cd0690e83f1dc4dde7698c3bd9d7fe98d However, this didn't change the option itself in tor (it's still SocksPort), and wasn't even uniform in the man page. Functionally this doesn't matter (tor's config options are case insensitive) but this is a pretty clear regression.
This commit is contained in:
Damian Johnson
parent
5812930dc1
commit
1193647ac8
|
|
@ -98,8 +98,8 @@ COMMAND-LINE OPTIONS
|
|||
Other options can be specified on the command-line in the format "--option
|
||||
value", in the format "option value", or in a configuration file. For
|
||||
instance, you can tell Tor to start listening for SOCKS connections on port
|
||||
9999 by passing --SOCKSPort 9999 or SOCKSPort 9999 to it on the command line,
|
||||
or by putting "SOCKSPort 9999" in the configuration file. You will need to
|
||||
9999 by passing --SocksPort 9999 or SocksPort 9999 to it on the command line,
|
||||
or by putting "SocksPort 9999" in the configuration file. You will need to
|
||||
quote options with spaces in them: if you want Tor to log all debugging
|
||||
messages to debug.log, you will probably need to say --Log 'debug file
|
||||
debug.log'.
|
||||
|
|
@ -125,17 +125,17 @@ the defaults file.
|
|||
|
||||
This rule is simple for options that take a single value, but it can become
|
||||
complicated for options that are allowed to occur more than once: if you
|
||||
specify four SOCKSPorts in your configuration file, and one more SOCKSPort on
|
||||
specify four SocksPorts in your configuration file, and one more SocksPort on
|
||||
the command line, the option on the command line will replace __all__ of the
|
||||
SOCKSPorts in the configuration file. If this isn't what you want, prefix
|
||||
SocksPorts in the configuration file. If this isn't what you want, prefix
|
||||
the option name with a plus sign (+), and it will be appended to the previous
|
||||
set of options instead. For example, setting SOCKSPort 9100 will use only
|
||||
port 9100, but setting +SOCKSPort 9100 will use ports 9100 and 9050 (because
|
||||
set of options instead. For example, setting SocksPort 9100 will use only
|
||||
port 9100, but setting +SocksPort 9100 will use ports 9100 and 9050 (because
|
||||
this is the default).
|
||||
|
||||
Alternatively, you might want to remove every instance of an option in the
|
||||
configuration file, and not replace it at all: you might want to say on the
|
||||
command line that you want no SOCKSPorts at all. To do that, prefix the
|
||||
command line that you want no SocksPorts at all. To do that, prefix the
|
||||
option name with a forward slash (/). You can use the plus sign (+) and the
|
||||
forward slash (/) in the configuration file and on the command line.
|
||||
|
||||
|
|
@ -968,7 +968,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]] **SOCKSPort** \['address':]__port__|**unix:**__path__|**auto** [_flags_] [_isolation flags_]::
|
||||
[[SocksPort]] **SocksPort** \['address':]__port__|**unix:**__path__|**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
|
||||
|
|
@ -983,7 +983,7 @@ The following options are useful only for clients (that is, if
|
|||
to use your computer as an open proxy. +
|
||||
+
|
||||
The _isolation flags_ arguments give Tor rules for which streams
|
||||
received on this SOCKSPort are allowed to share circuits with one
|
||||
received on this SocksPort are allowed to share circuits with one
|
||||
another. Recognized isolation flags are:
|
||||
**IsolateClientAddr**;;
|
||||
Don't share circuits with streams from a different
|
||||
|
|
@ -1010,11 +1010,11 @@ The following options are useful only for clients (that is, if
|
|||
If no other isolation rules would prevent it, allow streams
|
||||
on this port to share circuits with streams from every other
|
||||
port with the same session group. (By default, streams received
|
||||
on different SOCKSPorts, TransPorts, etc are always isolated from one
|
||||
on different SocksPorts, TransPorts, etc are always isolated from one
|
||||
another. This option overrides that behavior.)
|
||||
|
||||
[[OtherSOCKSPortFlags]]::
|
||||
Other recognized __flags__ for a SOCKSPort are:
|
||||
[[OtherSocksPortFlags]]::
|
||||
Other recognized __flags__ for a SocksPort are:
|
||||
**NoIPv4Traffic**;;
|
||||
Tell exits to not connect to IPv4 addresses in response to SOCKS
|
||||
requests on this connection.
|
||||
|
|
@ -1066,14 +1066,14 @@ The following options are useful only for clients (that is, if
|
|||
authentication" when IsolateSOCKSAuth is disabled, or when this
|
||||
option is set.
|
||||
|
||||
[[SOCKSListenAddress]] **SOCKSListenAddress** __IP__[:__PORT__]::
|
||||
[[SocksListenAddress]] **SocksListenAddress** __IP__[:__PORT__]::
|
||||
Bind to this address to listen for connections from Socks-speaking
|
||||
applications. (Default: 127.0.0.1) You can also specify a port (e.g.
|
||||
192.168.0.1:9100). This directive can be specified multiple times to bind
|
||||
to multiple addresses/ports. (DEPRECATED: As of 0.2.3.x-alpha, you can
|
||||
now use multiple SOCKSPort entries, and provide addresses for SOCKSPort
|
||||
entries, so SOCKSListenAddress no longer has a purpose. For backward
|
||||
compatibility, SOCKSListenAddress is only allowed when SOCKSPort is just
|
||||
now use multiple SocksPort entries, and provide addresses for SocksPort
|
||||
entries, so SocksListenAddress no longer has a purpose. For backward
|
||||
compatibility, SocksListenAddress is only allowed when SocksPort is just
|
||||
a port number.)
|
||||
|
||||
[[SocksPolicy]] **SocksPolicy** __policy__,__policy__,__...__::
|
||||
|
|
@ -1280,7 +1280,7 @@ The following options are useful only for clients (that is, if
|
|||
Use 0 if you don't want to allow NATD connections. Set the port
|
||||
to "auto" to have Tor pick a port for you. This directive can be
|
||||
specified multiple times to bind to multiple addresses/ports. See
|
||||
SOCKSPort for an explanation of isolation flags. +
|
||||
SocksPort for an explanation of isolation flags. +
|
||||
+
|
||||
This option is only for people who cannot use TransPort. (Default: 0)
|
||||
|
||||
|
|
@ -1308,7 +1308,7 @@ The following options are useful only for clients (that is, if
|
|||
doesn't handle arbitrary DNS request types. Set the port to "auto" to
|
||||
have Tor pick a port for
|
||||
you. This directive can be specified multiple times to bind to multiple
|
||||
addresses/ports. See SOCKSPort for an explanation of isolation
|
||||
addresses/ports. See SocksPort for an explanation of isolation
|
||||
flags. (Default: 0)
|
||||
|
||||
[[DNSListenAddress]] **DNSListenAddress** __IP__[:__PORT__]::
|
||||
|
|
|
|||
Loading…
Reference in New Issue