[tor-commits] [torspec] 02/06: Talk of "defined" rather than "recognized" auth types

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

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

nickm pushed a commit to branch main
in repository torspec.

commit 51fd440a19f1e41931049b72aae2d3cca0697d0c
Author: Ian Jackson <ijackson@xxxxxxxxxxxxxxxxxxxxxx>
AuthorDate: Mon Feb 6 15:06:41 2023 +0000

    Talk of "defined" rather than "recognized" auth types
    
    We're not the code, we're the spec.  We can define things, not
    recognise them.
---
 rend-spec-v3.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/rend-spec-v3.txt b/rend-spec-v3.txt
index 48d2ba3..b533895 100644
--- a/rend-spec-v3.txt
+++ b/rend-spec-v3.txt
@@ -1360,7 +1360,7 @@ Table of contents:
       A space-separated list of introduction-layer authentication types; see
       section [INTRO-AUTH] for more info. A client that does not support at
       least one of these authentication types will not be able to contact the
-      host. Recognized types are: 'password' and 'ed25519'.
+      host. Defined types are: 'password' and 'ed25519'.
 
      "single-onion-service"
 

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