diff options
| author | Roger Dingledine <arma@torproject.org> | 2005-11-17 03:18:18 +0000 |
|---|---|---|
| committer | Roger Dingledine <arma@torproject.org> | 2005-11-17 03:18:18 +0000 |
| commit | 6f060797414a4b89d64c53bf83f11674a212bcaf (patch) | |
| tree | 042a20bee59ae2193b28ec9bab8fa2fba37c3e75 /doc | |
| parent | 298da4497aed991a43be6265856562d65b07b83b (diff) | |
| download | tor-6f060797414a4b89d64c53bf83f11674a212bcaf.tar.gz tor-6f060797414a4b89d64c53bf83f11674a212bcaf.zip | |
fix a bug in the spec, and add a question about correct behavior. nick?
svn:r5404
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/tor-spec.txt | 7 |
1 files changed, 6 insertions, 1 deletions
diff --git a/doc/tor-spec.txt b/doc/tor-spec.txt index cd08d80b59..f0ad4134dd 100644 --- a/doc/tor-spec.txt +++ b/doc/tor-spec.txt @@ -450,7 +450,7 @@ connected at a different place. anything else? -RD] include forwarded data.) All RELAY cells pertaining to the same tunneled stream have the - same stream ID. StreamIDs are chosen randomly by the OP. RELAY + same stream ID. StreamIDs are chosen arbitrarily by the OP. RELAY cells that affect the entire circuit rather than a particular stream use a StreamID of zero. @@ -458,6 +458,10 @@ connected at a different place. anything else? -RD] the relay payload which contain real payload data. The remainder of the payload is padded with NUL bytes. + [XXX If we receive a relay command we don't recognize, the current Tor + implementation closes the circuit. Is that the right approach or the + wrong approach? -RD] + 5.2. Opening streams and transferring data To open a new anonymized TCP connection, the OP chooses an open @@ -974,3 +978,4 @@ B.2. ... and that we have no idea how to do. - Use a better AES mode that has built-in integrity checking, doesn't grow with the number of hops, is not patented, and is implemented and maintained by smart people. + |