aboutsummaryrefslogtreecommitdiff
path: root/doc/tor-spec.txt
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2006-01-05 21:32:33 +0000
committerRoger Dingledine <arma@torproject.org>2006-01-05 21:32:33 +0000
commit6b6af6c7d517e32bf054239e903b20ad5453454b (patch)
tree886700e96190036e48a94df84ddfce352469f48e /doc/tor-spec.txt
parent878962bee11eb47042d49ebd7df0d18d403c98c0 (diff)
downloadtor-6b6af6c7d517e32bf054239e903b20ad5453454b.tar.gz
tor-6b6af6c7d517e32bf054239e903b20ad5453454b.zip
todo and spec cleanups
svn:r5735
Diffstat (limited to 'doc/tor-spec.txt')
-rw-r--r--doc/tor-spec.txt5
1 files changed, 1 insertions, 4 deletions
diff --git a/doc/tor-spec.txt b/doc/tor-spec.txt
index 4b0931cdb0..e92b9d72e3 100644
--- a/doc/tor-spec.txt
+++ b/doc/tor-spec.txt
@@ -363,9 +363,6 @@ when do we rotate which keys (tls, link, etc)?
After a DESTROY cell has been processed, an OR ignores all data or
destroy cells for the corresponding circuit.
- (The rest of this section is not currently used; on errors, circuits
- are destroyed, not truncated.)
-
To tear down part of a circuit, the OP may send a RELAY_TRUNCATE cell
signaling a given OR (Stream ID zero). That OR sends a DESTROY
cell to the next node in the circuit, and replies to the OP with a
@@ -496,7 +493,7 @@ when do we rotate which keys (tls, link, etc)?
If the RELAY cell is recognized but the relay command is not
understood, the cell must be dropped and ignored. Its contents
- still count with respect to the digests, though. [Up until
+ still count with respect to the digests, though. [Before
0.1.1.10, Tor closed circuits when it received an unknown relay
command. Perhaps this will be more forward-compatible. -RD]