commit 09614e0c9db1d65c5f59c3a32c517f115b509021 Author: Nick Mathewson nickm@torproject.org Date: Tue Feb 23 08:42:31 2021 -0500
Tweak documentation on 40282 --- changes/ticket40282 | 12 ++++++------ doc/man/tor.1.txt | 6 ++---- 2 files changed, 8 insertions(+), 10 deletions(-)
diff --git a/changes/ticket40282 b/changes/ticket40282 index 4cfadcc2c0..2c69a77163 100644 --- a/changes/ticket40282 +++ b/changes/ticket40282 @@ -1,6 +1,6 @@ - o Major feature (relay): - - Relay do not use nor advertise a DirPort anymore. Only authorities do - because it is still used by them. Closes ticket 40282. - - Authority DirPort self reachability test has now been removed because - network reentry to that DirPort is not allowed anymore. - + o Removed features (relay): + - Because DirPorts are only used on authorities, relays no longer + advertise them. Similarly, self-testing for DirPorts has been disabled, + since an unreachable DirPort is no reason for a relay not to advertise + itself. (Configuring a DirPort will still work, for now.) Closes + ticket 40282. diff --git a/doc/man/tor.1.txt b/doc/man/tor.1.txt index 4b34790e00..d51183e04a 100644 --- a/doc/man/tor.1.txt +++ b/doc/man/tor.1.txt @@ -2795,11 +2795,9 @@ details.) + The same flags are supported here as are supported by ORPort. + - As of Tor 0.4.6.1-alpha, non authoritative relays (see + As of Tor 0.4.6.1-alpha, non-authoritative relays (see AuthoritativeDirectory) will not publish the DirPort but will still listen - on it so to avoid any unknown issues by closing all the sudden all - DirPorts on the network for most relays. We expect relays to stop - listening at some point in future stable releases. It is thus safe for you + on it. Clients don't use the DirPorts on relays, so it is safe for you to remove the DirPort from your torrc configuration.
[[DirPortFrontPage]] **DirPortFrontPage** __FILENAME__::