[tor-commits] [torspec/master] Change clause about recognized to 'may'
nickm at torproject.org
nickm at torproject.org
Tue Feb 13 14:07:09 UTC 2018
commit e4b7001bdfaf08f533f2716ac464f11792afc296
Author: Damian Johnson <atagar at torproject.org>
Date: Thu Feb 8 10:02:39 2018 -0800
Change clause about recognized to 'may'
Good point from Roger and Tim on...
https://trac.torproject.org/projects/tor/ticket/25171
---
tor-spec.txt | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/tor-spec.txt b/tor-spec.txt
index 2272c28..7aba3da 100644
--- a/tor-spec.txt
+++ b/tor-spec.txt
@@ -1446,8 +1446,9 @@ see tor-design.pdf.
The 'recognized' field is used for a simple indication for if the
cell still encrypted or not. When sending cells the unencrypted
'recognized' MUST be set to zero. When receiving and decrypting
- cells the 'recognized' will be zero if we're the endpoint the cell
- is destined for, and non-zero otherwise.
+ cells the 'recognized' MAY be zero if we're the endpoint the cell
+ is destined for (there's a 1/2^32 chance of encrypted bytes
+ coincidently being zero), and non-zero otherwise.
When 'recognized' in an unencrypted relay payload is zero the
'digest' field is computed as the first four bytes of the running
More information about the tor-commits
mailing list