From: Roger Dingledine Date: Wed, 20 Jan 2010 20:39:23 +0000 (-0500) Subject: make the 0.2.2.7-alpha changelog actually complete. X-Git-Tag: tor-0.2.2.8-alpha~10 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=2309d0caae3f53adf4f0b8d76785cb058e900e79;p=thirdparty%2Ftor.git make the 0.2.2.7-alpha changelog actually complete. weasel makes a good point. --- diff --git a/ChangeLog b/ChangeLog index aff869333c..c65f63c4f1 100644 --- a/ChangeLog +++ b/ChangeLog @@ -25,6 +25,10 @@ Changes in version 0.2.1.23 - 2010-0?-?? Changes in version 0.2.2.7-alpha - 2010-01-19 + o Directory authority changes: + - Rotate keys (both v3 identity and relay identity) for moria1 + and gabelmoo. + o Major features (performance): - We were selecting our guards uniformly at random, and then weighting which of our guards we'd use uniformly at random. This imbalance @@ -70,6 +74,11 @@ Changes in version 0.2.2.7-alpha - 2010-01-19 fetch -- rather than just at startup and then they slowly rot as the network changes. + o Major bugfixes: + - Stop bridge directory authorities from answering dbg-stability.txt + directory queries, which would let people fetch a list of all + bridge identities they track. Bugfix on 0.2.1.6-alpha. + o Minor features: - Log a notice when we get a new control connection. Now it's easier for security-conscious users to recognize when a local application