From 09bc858dd54101e645b31bf32fe463b73c38add2 Mon Sep 17 00:00:00 2001 From: David Goulet Date: Tue, 25 Apr 2017 13:49:05 -0400 Subject: config: Remove ExcludeSingleHopRelays 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 | 9 --------- 1 file changed, 9 deletions(-) (limited to 'doc') diff --git a/doc/tor.1.txt b/doc/tor.1.txt index e2e48088f4..54d0614d60 100644 --- a/doc/tor.1.txt +++ b/doc/tor.1.txt @@ -772,15 +772,6 @@ CLIENT OPTIONS The following options are useful only for clients (that is, if **SocksPort**, **TransPort**, **DNSPort**, or **NATDPort** is non-zero): -[[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 - to 0, these relays will be included. Note that these relays might be at - higher risk of being seized or observed, so they are not normally - included. Also note that relatively few clients turn off this option, - so using these relays might make your client stand out. - (Default: 1) - [[Bridge]] **Bridge** [__transport__] __IP__:__ORPort__ [__fingerprint__]:: When set along with UseBridges, instructs Tor to use the relay at "IP:ORPort" as a "bridge" relaying into the Tor network. If "fingerprint" -- cgit v1.2.3-54-g00ecf