aboutsummaryrefslogtreecommitdiff
path: root/doc/control-spec.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2005-06-24 18:04:00 +0000
committerNick Mathewson <nickm@torproject.org>2005-06-24 18:04:00 +0000
commit6602098e0365162087a8429c25724e6aacada490 (patch)
tree8094655390769d39ad2ceeb1fcd5183dfe4eb156 /doc/control-spec.txt
parent00a7a37c94e2cb788941202a1c3b824f6ebf6df0 (diff)
downloadtor-6602098e0365162087a8429c25724e6aacada490.tar
tor-6602098e0365162087a8429c25724e6aacada490.tar.gz
Describe how to detect v0 or v1 protocol
svn:r4478
Diffstat (limited to 'doc/control-spec.txt')
-rw-r--r--doc/control-spec.txt6
1 files changed, 5 insertions, 1 deletions
diff --git a/doc/control-spec.txt b/doc/control-spec.txt
index 81d1cd777..7bf7c50b3 100644
--- a/doc/control-spec.txt
+++ b/doc/control-spec.txt
@@ -635,7 +635,11 @@ about dns resolves, etc, so the controller can keep synced. -RD]
5.3. Backward compatibility
For backward compatibility with the "version 0" control protocol, Tor checks
- whether the third byte the first command is zero. If it is, Tor
+ whether the third octet the first command is zero. If it is, Tor
assumes that version 0 is in use. This feature is deprecated, and will be
removed in the 0.1.2.x Tor development series.
+ In order to detect which version of the protocol is supported controllers
+ should send the sequence [00 00 0D 0A]. This is a valid and unrecognized
+ command in both protocol versions, and implementations can detect which
+ error they have received.