mirror of
https://gitlab.torproject.org/tpo/core/tor.git
synced 2025-02-23 14:40:51 +01:00
fix a bug in the spec, and add a question about correct behavior. nick?
svn:r5404
This commit is contained in:
parent
298da4497a
commit
6f06079741
1 changed files with 6 additions and 1 deletions
|
@ -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.
|
||||
|
||||
|
|
Loading…
Add table
Reference in a new issue