[tor-commits] [torspec/master] Use correct terms from RFC's in spec.

[nickm@xxxxxxxxxxxxxx]

commit adb2bf39305f7e97d4dc58abe91b9ae6939075a1
Author: Linus Nordberg <linus@xxxxxxxxxxx>
Date:   Tue Jul 12 09:34:00 2011 -0400

    Use correct terms from RFC's in spec.
---
 socks-extensions.txt |   11 ++++++-----
 1 files changed, 6 insertions(+), 5 deletions(-)

diff --git a/socks-extensions.txt b/socks-extensions.txt
index 60695e5..f587d9c 100644
--- a/socks-extensions.txt
+++ b/socks-extensions.txt
@@ -31,11 +31,12 @@ Tor's extensions to the SOCKS protocol
   SOCKS5:
   - The (SOCKS5) "UDP ASSOCIATE" command is not supported.
   - IPv6 is not supported in CONNECT commands.
-  - The "NO AUTHENTICATION" (SOCKS5) authentication method [00] is supported.
-    As of Tor 0.2.3.2-alpha, the "USERNAME/PASSWORD" (SOCKS5) authentication
-    method [02] is supported too. As an extension to support some broken
-    clients, we allow clients to pass "USERNAME/PASSWORD" authentication to
-    us even if no authentication was selected.
+  - The "NO AUTHENTICATION REQUIRED" (SOCKS5) authentication method [00] is
+    supported; and as of Tor 0.2.3.2-alpha, the "USERNAME/PASSWORD" (SOCKS5)
+    authentication method [02] is supported too. Any credentials passed to
+    the latter are ignored. As an extension to support some broken clients,
+    we allow clients to pass "USERNAME/PASSWORD" authentication to us even if
+    no authentication was selected.
 
 2. Name lookup
 

_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits