[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-commits] [torspec] 01/03: Clarify that ESTABLISH_INTRO signature doesn't cover SIG_LEN.

This is an automated email from the git hooks/post-receive script.

dgoulet pushed a commit to branch main
in repository torspec.

commit ba581c95bfdad21f2f0e9c233af0ccd90ab34518
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
AuthorDate: Wed Mar 1 07:42:22 2023 -0500

    Clarify that ESTABLISH_INTRO signature doesn't cover SIG_LEN.
    
    The previous wording implied that SIG_LEN was also signed, which
    it isn't.
---
 rend-spec-v3.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/rend-spec-v3.txt b/rend-spec-v3.txt
index 5a130f9..01a48df 100644
--- a/rend-spec-v3.txt
+++ b/rend-spec-v3.txt
@@ -1638,8 +1638,8 @@ Table of contents:
    SIG_LEN is the length of the signature.
 
    SIG is a signature, using AUTH_KEY, of all contents of the cell, up
-   to but not including SIG. These contents are prefixed with the string
-   "Tor establish-intro cell v1".
+   to but not including SIG_LEN and SIG. These contents are prefixed
+   with the string "Tor establish-intro cell v1".
 
    Upon receiving an ESTABLISH_INTRO cell, a Tor node first decodes the
    key and the signature, and checks the signature. The node must reject

-- 
To stop receiving notification emails like this one, please contact
the administrator of this repository.
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits