[tor-commits] [torspec] 04/04: rend-spec: clarify how dir info may be used to confirm linkspecs

[gitolite role via tor-commits <tor-commits@xxxxxxxxxxxxxxxxxxxx>]

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

dgoulet pushed a commit to branch main
in repository torspec.

commit 70ca4e9dcb2b37e1fa68a3cdac56dfe244e54ab1
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
AuthorDate: Wed Mar 22 14:30:22 2023 -0400

    rend-spec: clarify how dir info may be used to confirm linkspecs
    
    Specifically, you can look at the directory to see if somebody is
    lying about a relay (mismatched IDs, etc), but you can't modify
    the list of linkspecs.
---
 rend-spec-v3.txt | 8 ++++++++
 1 file changed, 8 insertions(+)

diff --git a/rend-spec-v3.txt b/rend-spec-v3.txt
index 4ba88d7..4a12343 100644
--- a/rend-spec-v3.txt
+++ b/rend-spec-v3.txt
@@ -1403,6 +1403,10 @@ Table of contents:
           this list of link specifiers verbatim, in the same order as given
           here.
 
+          The client MAY reject the list of link specifiers if it is
+          inconsistent with relay information from the directory, but SHOULD
+          NOT modify it.
+
         "onion-key" SP "ntor" SP key NL
 
           [Exactly once per introduction point]
@@ -1915,6 +1919,10 @@ Table of contents:
    sent verbatim when extending to the rendezvous point, in the same order
    received.
 
+   The service MAY reject the list of link specifiers if it is
+   inconsistent with relay information from the directory, but SHOULD
+   NOT modify it.
+
    The ONION_KEY_TYPE field is:
 
       [01] NTOR:          ONION_KEY is 32 bytes long.

-- 
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