From: Roger Dingledine Date: Fri, 18 Sep 2009 07:05:52 +0000 (-0400) Subject: clarify our rules for assigning the Named flag X-Git-Tag: tor-0.2.2.2-alpha~14 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=6750f7e8b1eb795c1f85eee8b96a0516de917cc1;p=thirdparty%2Ftor.git clarify our rules for assigning the Named flag --- diff --git a/contrib/auto-naming/README b/contrib/auto-naming/README index 77e6af6483..df78491a79 100644 --- a/contrib/auto-naming/README +++ b/contrib/auto-naming/README @@ -9,9 +9,9 @@ This toolset allows automatic maintaining of a binding list of nicknames to identity keys, implementing Tor proposal 123[1]. The rules are simple: - - A router claiming to be Bob is named (i.e. added to the binding list) + - A router claiming to be Bob becomes named (i.e. added to the binding list) if there currently does not exist a different binding for that - nickname, the router has been around for a bit (2 weeks), no other + nickname, the router has been around for a bit (2 weeks), and no other router has used that nickname in a while (1 month). - A binding is removed if the server that owns it has not been seen in a long time (6 months).