diff options
| author | Nick Mathewson <nickm@torproject.org> | 2007-03-15 16:27:57 +0000 |
|---|---|---|
| committer | Nick Mathewson <nickm@torproject.org> | 2007-03-15 16:27:57 +0000 |
| commit | e50e6b4e3c3bf881665126696d5b4fa35859b666 (patch) | |
| tree | 61950dc9fecad1001a6e72c4bc58c08229c5466c /doc | |
| parent | a9d0479d96b456f64b0a5404ba29a9b342776671 (diff) | |
| download | tor-e50e6b4e3c3bf881665126696d5b4fa35859b666.tar.gz tor-e50e6b4e3c3bf881665126696d5b4fa35859b666.zip | |
r12182@catbus: nickm | 2007-03-15 10:58:12 -0400
Clarify section of dir-spec.txt that explains how "v" resolution happens.
svn:r9829
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/spec/dir-spec.txt | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/spec/dir-spec.txt b/doc/spec/dir-spec.txt index bd3d57a34d..be13e4ce8c 100644 --- a/doc/spec/dir-spec.txt +++ b/doc/spec/dir-spec.txt @@ -841,9 +841,9 @@ $Id$ feature is supported by the router or protocol versions in more than half of the live networkstatus's "v" entries for that router. In other words, if the "v" entries for some router are: - v Tor 0.0.8pre1 - v Tor 0.1.2.11 - v FutureProtocolDescription 99 + v Tor 0.0.8pre1 (from authority 1) + v Tor 0.1.2.11 (from authority 2) + v FutureProtocolDescription 99 (from authority 3) then the client should believe that the router supports any feature supported by 0.1.2.11. |