summaryrefslogtreecommitdiff
path: root/ChangeLog
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2007-11-17 01:53:33 +0000
committerRoger Dingledine <arma@torproject.org>2007-11-17 01:53:33 +0000
commitd6f8ba25c92430cbc0ba9f14da4c7518e309eb0e (patch)
tree942c088a3e105db8fe772081ba5c06ab1eeac40f /ChangeLog
parentd09439872d81046d6edee7a4fa03fc4b68db8ab3 (diff)
downloadtor-d6f8ba25c92430cbc0ba9f14da4c7518e309eb0e.tar.gz
tor-d6f8ba25c92430cbc0ba9f14da4c7518e309eb0e.zip
back out r12509 and fix a better bug instead:
When authorities detected more than two relays running on the same IP address, they were clearing all the status flags but forgetting to clear the "hsdir" flag. So clients were being told that a given relay was the right choice for a v2 hsdir lookup, yet they never had its descriptor because it was marked as 'not running' in the consensus. svn:r12515
Diffstat (limited to 'ChangeLog')
-rw-r--r--ChangeLog8
1 files changed, 6 insertions, 2 deletions
diff --git a/ChangeLog b/ChangeLog
index 6eb820ec50..c4f18ba8b0 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -10,8 +10,12 @@ Changes in version 0.2.0.12-alpha - 2007-11-??
newly picked entry guard. Reported by Mike Perry.
- Changing the ExitPolicyRejectPrivate setting should cause us to
rebuild the descriptor.
- - When picking v2 hidden service directories, don't pick ones that
- aren't listed as Running.
+ - When authorities detected more than two relays running on the same
+ IP address, they were clearing all the status flags but forgetting
+ to clear the "hsdir" flag. So clients were being told that a
+ given relay was the right choice for a v2 hsdir lookup, yet they
+ never had its descriptor because it was marked as 'not running'
+ in the consensus.
- If we're trying to fetch a bridge descriptor and there's no way
the bridge authority could help us (for example, we don't know
a digest, or there is no bridge authority), don't be so eager to