mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2024-11-10 21:23:58 +01:00
9b64227ffd
rransom noticed that a change of ORPort is just as bad as a change of IP address from a client's perspective, because both mean that the relay is not available to them while the new information hasn't propagated. Change the bug1035 fix accordingly. Also make sure we don't log a bridge's IP address (which might happen when we are the bridge authority).
14 lines
713 B
Plaintext
14 lines
713 B
Plaintext
o Minor features (authorities)
|
|
- Take altered router IP addresses and ORPorts into account when
|
|
determining router stability. Previously, if a router changed
|
|
its IP or ORPort, the authorities would not treat it as having
|
|
any downtime for the purposes of stability calculation, whereas
|
|
clients would experience downtime since the change could take a
|
|
while to propagate to them. Resolves issue 1035.
|
|
o Minor bugfixes (authorities)
|
|
- Try to be more robust to hops back in time when calculating
|
|
router stability. Previously, if a run of uptime or downtime
|
|
appeared to be negative, the calculation could give incorrect
|
|
results. Bugfix on 0.2.0.6-alpha.
|
|
|