aboutsummaryrefslogtreecommitdiff
path: root/tor-spec.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2014-02-20 13:51:19 +0000
committerNick Mathewson <nickm@torproject.org>2014-02-20 14:00:35 +0000
commit9492dbb6efcdcc7b60325dcd12665d10a9a53a5c (patch)
tree00f531b61af950fefdbfc98db44da97e0b9e8fdb /tor-spec.txt
parent01c536fa3d931401258465177b61720b1b033179 (diff)
downloadtorspec-9492dbb6efcdcc7b60325dcd12665d10a9a53a5c.tar.gz
torspec-9492dbb6efcdcc7b60325dcd12665d10a9a53a5c.zip
tor-spec: link versions above 3 exist. (see sec 4.1)
Diffstat (limited to 'tor-spec.txt')
-rw-r--r--tor-spec.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/tor-spec.txt b/tor-spec.txt
index 1c10d1d..c3b96a3 100644
--- a/tor-spec.txt
+++ b/tor-spec.txt
@@ -216,8 +216,8 @@ see tor-design.pdf.
* The certificate's public key modulus is longer than 1024 bits.
The initiator then sends a VERSIONS cell to the responder, which then
replies with a VERSIONS cell; they have then negotiated a Tor
- protocol version. Assuming that the version they negotiate is 3 (the
- only one specified for use with this handshake right now), the
+ protocol version. Assuming that the version they negotiate is 3 or higher
+ (the only ones specified for use with this handshake right now), the
responder sends a CERTS cell, an AUTH_CHALLENGE cell, and a NETINFO
cell to the initiator, which may send either CERTS, AUTHENTICATE,
NETINFO if it wants to authenticate, or just NETINFO if it does not.