aboutsummaryrefslogtreecommitdiff
path: root/doc/rend-spec.txt
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2004-04-28 20:01:54 +0000
committerRoger Dingledine <arma@torproject.org>2004-04-28 20:01:54 +0000
commitfd0d48e4843de1ad8d6dda7ff91bd505887d5889 (patch)
treefc7459fc37fe187f09334e6da7e89a0965655063 /doc/rend-spec.txt
parent25d5425fdb85071069dc8ec9dd02209b8205c8ea (diff)
downloadtor-fd0d48e4843de1ad8d6dda7ff91bd505887d5889.tar
tor-fd0d48e4843de1ad8d6dda7ff91bd505887d5889.tar.gz
clarify the hybrid encryption in our spec
svn:r1736
Diffstat (limited to 'doc/rend-spec.txt')
-rw-r--r--doc/rend-spec.txt10
1 files changed, 4 insertions, 6 deletions
diff --git a/doc/rend-spec.txt b/doc/rend-spec.txt
index c428864d8..ac2b0aca8 100644
--- a/doc/rend-spec.txt
+++ b/doc/rend-spec.txt
@@ -255,12 +255,10 @@ Tor Rendezvous Spec
PK_ID is the hash of Bob's public key. RP is NUL-padded.
- The data is encrypted to Bob's PK as follows: Suppose Bob's PK is L octets
- long. If the data to be encrypted is shorter than L-42, then it is
- encrypted directly (with OAEP padding). If the data is at least as long
- as L-42, then a randomly generated 16-byte symmetric key is prepended to
- the data, after which the first L-16-42 bytes of the data are encrypted with
- Bob's PK; and the rest of the data is encrypted with the symmetric key.
+ The hybrid encryption to Bob's PK works just like the hybrid
+ encryption in CREATE cells (see main spec). Thus the payload of the
+ RELAY_INTRODUCE1 cell on the wire will contain 20+42+16+20+20+128=246
+ bytes.
1.9. Introduction: From the Introduction Point to Bob's OP