aboutsummaryrefslogtreecommitdiff
path: root/doc/tor.1.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2011-07-06 10:56:47 -0400
committerNick Mathewson <nickm@torproject.org>2011-07-06 10:56:47 -0400
commiteee942c5bed2d93cd4413c8c2fb13539d5816b69 (patch)
tree3d25bec352992e6750178ece7db3b37fd1fa92aa /doc/tor.1.txt
parentab8c0d4c9e23b1c4e2d9e56d87b1b61505a2a8db (diff)
parent1a016c923348c125d79d2e92c2ae9fa2fa2a5af8 (diff)
downloadtor-eee942c5bed2d93cd4413c8c2fb13539d5816b69.tar
tor-eee942c5bed2d93cd4413c8c2fb13539d5816b69.tar.gz
Merge remote-tracking branch 'origin/maint-0.2.2'
Diffstat (limited to 'doc/tor.1.txt')
-rw-r--r--doc/tor.1.txt14
1 files changed, 7 insertions, 7 deletions
diff --git a/doc/tor.1.txt b/doc/tor.1.txt
index 6454e6be4..9607632e1 100644
--- a/doc/tor.1.txt
+++ b/doc/tor.1.txt
@@ -527,14 +527,14 @@ The following options are useful only for clients (that is, if
patterns of nodes to avoid when building a circuit.
(Example:
ExcludeNodes SlowServer, $ EFFFFFFFFFFFFFFF, \{cc}, 255.254.0.0/8) +
-+
+ +
By default, this option is treated as a preference that Tor is allowed
to override in order to keep working.
For example, if you try to connect to a hidden service,
but you have excluded all of the hidden service's introduction points,
Tor will connect to one of them anyway. If you do not want this
behavior, set the StrictNodes option (documented below). +
-+
+ +
Note also that if you are a relay, this (and the other node selection
options below) only affects your own circuits that Tor builds for you.
Clients can still build circuits through you to any node. Controllers
@@ -552,22 +552,22 @@ The following options are useful only for clients (that is, if
A list of identity fingerprints, nicknames, country codes and address
patterns of nodes to use as exit node---that is, a
node that delivers traffic for you outside the Tor network. +
-+
+ +
Note that if you list too few nodes here, or if you exclude too many exit
nodes with ExcludeExitNodes, you can degrade functionality. For example,
if none of the exits you list allows traffic on port 80 or 443, you won't
be able to browse the web. +
-+
+ +
Note also that not every circuit is used to deliver traffic outside of
the Tor network. It is normal to see non-exit circuits (such as those
used to connect to hidden services, those that do directory fetches,
those used for relay reachability self-tests, and so on) that end
at a non-exit node. To
keep a node from being used entirely, see ExcludeNodes and StrictNodes. +
-+
+ +
The ExcludeNodes option overrides this option: any node listed in both
ExitNodes and ExcludeNodes is treated as excluded. +
-+
+ +
The .exit address notation, if enabled via AllowDotExit, overrides
this option.
@@ -578,7 +578,7 @@ The following options are useful only for clients (that is, if
circuits except for direct connections to directory servers. The Bridge
option overrides this option; if you have configured bridges and
UseBridges is 1, the Bridges are used as your entry nodes. +
-+
+ +
The ExcludeNodes option overrides this option: any node listed in both
EntryNodes and ExcludeNodes is treated as excluded.