aboutsummaryrefslogtreecommitdiff
path: root/spec/tor-spec/relay-cells.md
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2023-11-08 14:48:11 -0500
committerNick Mathewson <nickm@torproject.org>2023-11-09 09:12:48 -0500
commitcae2c281238e798d3a2614f241e888e92b53ea4e (patch)
treee2b0e0d2463b62e029099547624d4d703912176b /spec/tor-spec/relay-cells.md
parent919d193f1c85aef1387c3c3498b23b886abb7489 (diff)
downloadtorspec-cae2c281238e798d3a2614f241e888e92b53ea4e.tar.gz
torspec-cae2c281238e798d3a2614f241e888e92b53ea4e.zip
Finish revising cell-packet-format.
Diffstat (limited to 'spec/tor-spec/relay-cells.md')
-rw-r--r--spec/tor-spec/relay-cells.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/spec/tor-spec/relay-cells.md b/spec/tor-spec/relay-cells.md
index add1f42..9f1abb2 100644
--- a/spec/tor-spec/relay-cells.md
+++ b/spec/tor-spec/relay-cells.md
@@ -104,11 +104,12 @@ 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 [Cell Packet format](./cell-packet-format.md#cell-packet-format).
-The 'Padding' field is used to make relay cell contents unpredictable, to
+<span id="relay-cell-padding">The
+'Padding' field is used to make relay cell contents unpredictable, to
avoid certain attacks (see proposal 289 for rationale). Implementations
SHOULD fill this field with four zero-valued bytes, followed by as many
random bytes as will fit. (If there are fewer than 4 bytes for padding,
-then they should all be filled with zero.
+then they should all be filled with zero.</span>
Implementations MUST NOT rely on the contents of the 'Padding' field.