[or-cvs] fix some more bugs in the spec
Roger Dingledine
arma at seul.org
Mon May 10 05:57:33 UTC 2004
Update of /home/or/cvsroot/doc
In directory moria.mit.edu:/home2/arma/work/onion/cvs/doc
Modified Files:
tor-spec.txt
Log Message:
fix some more bugs in the spec
Index: tor-spec.txt
===================================================================
RCS file: /home/or/cvsroot/doc/tor-spec.txt,v
retrieving revision 1.54
retrieving revision 1.55
diff -u -d -r1.54 -r1.55
--- tor-spec.txt 5 May 2004 06:53:44 -0000 1.54
+++ tor-spec.txt 10 May 2004 05:57:31 -0000 1.55
@@ -311,9 +311,9 @@
either an 'exit node' or a non-edge node), it de/encrypts the payload
with AES/CTR, as follows:
'Forward' relay cell (same direction as CREATE):
- Use Kf as key; encrypt.
+ Use Kf as key; decrypt.
'Back' relay cell (opposite direction from CREATE):
- Use Kb as key; decrypt.
+ Use Kb as key; encrypt.
The OR then decides whether it recognizes the relay cell, by
inspecting the payload as described in section 5.1 below. If the OR
@@ -323,11 +323,11 @@
encounters an unrecognized relay cell, an error has occurred: the OR
sends a DESTROY cell to tear down the circuit.
- When a relay cell arrives at an OP, it the OP encrypts the length and
- payload fields with AES/CTR as follows:
+ When a relay cell arrives at an OP, the OP decrypts the payload
+ with AES/CTR as follows:
OP receives data cell:
For I=N...1,
- Encrypt with Kb_I. If the payload is recognized (see
+ Decrypt with Kb_I. If the payload is recognized (see
section 5.1), then stop and process the payload.
For more information, see section 5 below.
More information about the tor-commits
mailing list