mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-10 21:23:58 +01:00
Tweak documentation on 40282
This commit is contained in:
parent
4321755de7
commit
09614e0c9d
@ -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.
|
||||
|
@ -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__::
|
||||
|
Loading…
Reference in New Issue
Block a user