[tor-commits] [tor/release-0.2.2] fixups on the bug1090-general changes

arma at torproject.org arma at torproject.org
Wed Apr 27 18:38:51 UTC 2011


commit ee713b046cdd58e695db821bc643a0467acb52e9
Author: Roger Dingledine <arma at torproject.org>
Date:   Wed Apr 27 14:38:55 2011 -0400

    fixups on the bug1090-general changes
---
 changes/bug1090-general |    7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/changes/bug1090-general b/changes/bug1090-general
index 4656315..2ca5493 100644
--- a/changes/bug1090-general
+++ b/changes/bug1090-general
@@ -12,7 +12,7 @@
 	. "Exit", in the context of ExitNodes and ExcludeExitNodes,
 	   means a node that delivers user traffic outside the Tor
 	   network.
-	. "Entry", in the context of EntryNodes and ExcludeEntryNodes,
+	. "Entry", in the context of EntryNodes,
 	  means a node used as the first hop of a multihop circuit:
 	  it doesn't include direct connections to directory servers.
 	. "ExcludeNodes" applies to all nodes.
@@ -48,9 +48,10 @@
          and to rendezvous points selected by hidden service users.
          This can make your hidden service less reliable: use it with
          caution!
-       . If we have used ExcludeNodes on ourself, do not try self-tests.
+       . If we have used ExcludeNodes on ourself, do not try relay
+         reachability self-tests.
        . If we have excluded all the directory authorities, we will
-         not even try to upload our descriptor if we're a server.
+         not even try to upload our descriptor if we're a relay.
        . Do not honor .exit requests to an excluded node.
 
     - Remove a misfeature that caused us to ignore the Fast/Stable flags



More information about the tor-commits mailing list