commit d760e91d1d8ef9f50ec09d53d05c4e2d4d36f3c7 Author: Nick Mathewson nickm@torproject.org Date: Thu Apr 28 23:02:39 2011 -0400
Edit the changelog a little more --- ChangeLog | 14 +++++++------- 1 files changed, 7 insertions(+), 7 deletions(-)
diff --git a/ChangeLog b/ChangeLog index 4571fc5..fe2c7e3 100644 --- a/ChangeLog +++ b/ChangeLog @@ -21,15 +21,15 @@ Changes in version 0.2.2.25-alpha - 2011-04-28 if it is followed in the blob we're parsing by an unparsable microdescriptor. Fixes an issue reported in a comment on bug 2954. Bugfix on 0.2.2.6-alpha; fix by "cypherpunks". - - If the Nickname configuration option isn't given, Tor would pick - a nickname based on the local hostname as the nickname for a relay. + - If the Nickname configuration option isn't given, Tor would pick a + nickname based on the local hostname as the nickname for a relay. Because nicknames are not very important in today's Tor and the "Unnamed" nickname has been implemented, this is now problematic - behavior: It leaks information about the hostname without being - useful at all. Bugfix on 0.1.2.2-alpha, which introduced the - Unnamed nickname. Fixes bug 2979, reported by tagnaq. + behavior: It leaks information about the hostname without being useful + at all. Fixes bug 2979; bugfix on 0.1.2.2-alpha, which introduced the + Unnamed nickname. Reported by tagnaq. - Fix an uncommon assertion failure when running with DNSPort under - heavy load. Fixes bug 2933; bugfix on 2.0.1-alpha. + heavy load. Fixes bug 2933; bugfix on 0.2.0.1-alpha. - Avoid linkability based on cached hidden service descriptors: forget all hidden service descriptors cached as a client when processing a SIGNAL NEWNYM command. Fixes bug 3000; bugfix on 0.0.6. @@ -41,7 +41,7 @@ Changes in version 0.2.2.25-alpha - 2011-04-28 contributions to the network.
o Major features and bugfixes (node selection): - - Revise and unify the meaning of the ExitNodes, EntryNodes, + - Revise and reconcile the meaning of the ExitNodes, EntryNodes, ExcludeEntryNodes, ExcludeExitNodes, ExcludeNodes, and StrictNodes options. Previously, we had been ambiguous in describing what counted as an "exit" node, and what operations exactly "StrictNodes