aboutsummaryrefslogtreecommitdiff
path: root/doc/tor-spec.txt
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2005-11-17 03:43:10 +0000
committerRoger Dingledine <arma@torproject.org>2005-11-17 03:43:10 +0000
commitae937b4e40b9a86383c623193722b6df695ba769 (patch)
tree05154432507941e328ff72796330072eb49c94b6 /doc/tor-spec.txt
parentbed777375b665f210204635231b15c14fb34108e (diff)
downloadtor-ae937b4e40b9a86383c623193722b6df695ba769.tar
tor-ae937b4e40b9a86383c623193722b6df695ba769.tar.gz
and note that older tors break the spec in that way
svn:r5407
Diffstat (limited to 'doc/tor-spec.txt')
-rw-r--r--doc/tor-spec.txt4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/tor-spec.txt b/doc/tor-spec.txt
index 82322d2a1..86ea88593 100644
--- a/doc/tor-spec.txt
+++ b/doc/tor-spec.txt
@@ -459,7 +459,9 @@ connected at a different place. anything else? -RD]
the payload is padded with NUL bytes.
If the RELAY cell is recognized but the relay command is not
- understood, the cell must be dropped and ignored.
+ understood, the cell must be dropped and ignored. [Up until
+ 0.1.1.10, Tor closed circuits when it received an unknown relay
+ command. Perhaps this will be more forward-compatible. -RD]
5.2. Opening streams and transferring data