Manpage: refer to ExcludeExitNodes, not the nonexistent ExcludeEntryNodes

Spotted on tor-talk by "hamahangi".
This commit is contained in:
Nick Mathewson 2013-04-13 18:27:08 -04:00
parent 97246a5b6d
commit 8aded5b07c
2 changed files with 6 additions and 2 deletions

View File

@ -0,0 +1,4 @@
o Documentation fixes:
- Fix the GeoIPExcludeUnknown documentation to refer to ExcludeExitNodes
rather than the currently nonexistent ExcludeEntryNodes. Spotted by
"hamahangi" on tor-talk.

View File

@ -695,10 +695,10 @@ The following options are useful only for clients (that is, if
**GeoIPExcludeUnknown** **0**|**1**|**auto**:: **GeoIPExcludeUnknown** **0**|**1**|**auto**::
If this option is set to 'auto', then whenever any country code is set in If this option is set to 'auto', then whenever any country code is set in
ExcludeNodes or ExcludeEntryNodes, all nodes with unknown country (\{??} and ExcludeNodes or ExcludeExitNodes, all nodes with unknown country (\{??} and
possibly \{A1}) are treated as excluded as well. If this option is set to possibly \{A1}) are treated as excluded as well. If this option is set to
'1', then all unknown countries are treated as excluded in ExcludeNodes '1', then all unknown countries are treated as excluded in ExcludeNodes
and ExcludeEntryNodes. This option has no effect when a GeoIP file isn't and ExcludeExitNodes. This option has no effect when a GeoIP file isn't
configured or can't be found. (Default: auto) configured or can't be found. (Default: auto)
**ExitNodes** __node__,__node__,__...__:: **ExitNodes** __node__,__node__,__...__::