aboutsummaryrefslogtreecommitdiff
path: root/tor-spec.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2020-06-26 10:19:37 -0400
committerNick Mathewson <nickm@torproject.org>2020-06-26 10:20:48 -0400
commit7479cd9e4e9c8110e4babd40cb1da888eb00c390 (patch)
treeac1282f5e7d009fb9d55f7b109b2a13be1fda887 /tor-spec.txt
parent7146ead1ecb564c00d1eac99f92b58e7674da40f (diff)
downloadtorspec-7479cd9e4e9c8110e4babd40cb1da888eb00c390.tar.gz
torspec-7479cd9e4e9c8110e4babd40cb1da888eb00c390.zip
Add a sentence about how the digest is calculated; closes tor#32830
Diffstat (limited to 'tor-spec.txt')
-rw-r--r--tor-spec.txt7
1 files changed, 4 insertions, 3 deletions
diff --git a/tor-spec.txt b/tor-spec.txt
index 9b2c7b3..40ea4cc 100644
--- a/tor-spec.txt
+++ b/tor-spec.txt
@@ -1617,9 +1617,10 @@ see tor-design.pdf.
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
- (taken with the digest field set to zero). If the digest
- is correct, the cell is considered "recognized" for the purposes of
- decryption (see section 5.5 above).
+ (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).
(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