From 2b9823b3106df2cf23e2de13ae9a9b6d12607ce4 Mon Sep 17 00:00:00 2001 From: David Goulet Date: Tue, 25 Apr 2017 13:22:35 -0400 Subject: config: Remove AllowInvalidNodes option Deprecated in 0.2.9.2-alpha, this commits changes it as OBSOLETE() and cleans up the code associated with it. Partially fixes #22060 Signed-off-by: David Goulet --- doc/tor.1.txt | 7 ------- 1 file changed, 7 deletions(-) (limited to 'doc') diff --git a/doc/tor.1.txt b/doc/tor.1.txt index c7692379b1..012c5b93d6 100644 --- a/doc/tor.1.txt +++ b/doc/tor.1.txt @@ -772,13 +772,6 @@ CLIENT OPTIONS The following options are useful only for clients (that is, if **SocksPort**, **TransPort**, **DNSPort**, or **NATDPort** is non-zero): -[[AllowInvalidNodes]] **AllowInvalidNodes** **entry**|**exit**|**middle**|**introduction**|**rendezvous**|**...**:: - If some Tor servers are obviously not working right, the directory - authorities can manually mark them as invalid, meaning that it's not - recommended you use them for entry or exit positions in your circuits. You - can opt to use them in some circuit positions, though. The default is - "middle,rendezvous", and other choices are not advised. - [[ExcludeSingleHopRelays]] **ExcludeSingleHopRelays** **0**|**1**:: This option controls whether circuits built by Tor will include relays with the AllowSingleHopExits flag set to true. If ExcludeSingleHopRelays is set -- cgit v1.2.3-54-g00ecf