diff options
author | Jim Newsome <jnewsome@torproject.org> | 2023-11-06 15:10:54 -0600 |
---|---|---|
committer | Jim Newsome <jnewsome@torproject.org> | 2023-11-06 15:10:54 -0600 |
commit | 63f3d7628f273ff6fa1f86c8e7eb6897d9384222 (patch) | |
tree | e45d08a0584752acfd7cc345b97dcd1259521d06 /spec/tor-spec/relay-cells.md | |
parent | 5497deb54e8acec476590445f660c703c6b9c1f6 (diff) | |
download | torspec-63f3d7628f273ff6fa1f86c8e7eb6897d9384222.tar.gz torspec-63f3d7628f273ff6fa1f86c8e7eb6897d9384222.zip |
tor-spec: replace Section x.y.z with links
This replaces most of the occurences found with
`git grep '[sS]ection\s[0-9]'` in tor-spec.
I left instances inside code blocks for follow-up MRs.
Diffstat (limited to 'spec/tor-spec/relay-cells.md')
-rw-r--r-- | spec/tor-spec/relay-cells.md | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/spec/tor-spec/relay-cells.md b/spec/tor-spec/relay-cells.md index ce339b2..add1f42 100644 --- a/spec/tor-spec/relay-cells.md +++ b/spec/tor-spec/relay-cells.md @@ -75,11 +75,13 @@ decrypted relay payload is zero, the 'digest' field is computed as the first four bytes of the running digest of all the bytes that have been destined for this hop of the circuit or originated from this hop of the circuit, seeded from Df or Db respectively (obtained in -section 5.2 above), and including this RELAY cell's entire payload +[Setting circuit keys](./setting-circuit-keys.md#setting-circuit-keys)), +and including this RELAY cell's entire payload (taken with the digest field set to zero). Note that these digests _do_ include the padding bytes at the end of the cell, not only those up to "Len". If the digest is correct, the cell is considered "recognized" -for the purposes of decryption (see section 5.5 above). +for the purposes of decryption (see +[Routing relay cells](./routing-relay-cells.md#routing-relay-cells)). (The digest does not include any bytes from relay cells that do not start or end at this hop of the circuit. That is, it does not @@ -94,13 +96,13 @@ entire circuit rather than a particular stream use a StreamID of zero -- they are marked in the table above as "\[control\]" style cells. (Sendme cells are marked as "sometimes control" because they can include a StreamID or not depending on their purpose -- see -Section 7.) +[Flow control](./flow-control.md#flow-control).) The 'Length' field of a relay cell contains the number of bytes in the relay payload which contain real payload data. The remainder of the unencrypted payload is padded with padding bytes. Implementations handle padding bytes of unencrypted relay cells as they do padding -bytes for other cell types; see Section 3. +bytes for other cell types; see [Cell Packet format](./cell-packet-format.md#cell-packet-format). The 'Padding' field is used to make relay cell contents unpredictable, to avoid certain attacks (see proposal 289 for rationale). Implementations |