[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [torspec/master] correct prop244 and make it more specific
commit 0760e80a360ad1d315b48099f3ebd5e511516b2d
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date: Thu Sep 22 11:02:40 2016 -0400
correct prop244 and make it more specific
---
proposals/244-use-rfc5705-for-tls-binding.txt | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/proposals/244-use-rfc5705-for-tls-binding.txt b/proposals/244-use-rfc5705-for-tls-binding.txt
index d1a51fe..c4369b3 100644
--- a/proposals/244-use-rfc5705-for-tls-binding.txt
+++ b/proposals/244-use-rfc5705-for-tls-binding.txt
@@ -21,7 +21,7 @@ Status: Accepted
and TYPE field to be determined, that works the same as our current
"RSA-SHA256-TLSSecret" authentication, except for these fields:
- TYPE is a different constant string.
+ TYPE is a different constant string, "AUTH0002".
TLSSECRETS is replaced by the output of the Exporter function in
RFC5705, using as its inputs:
@@ -29,10 +29,10 @@ Status: Accepted
* The context value equal to the client's identity key digest.
* The length 32.
- I propose that proposal 224's section on authenticating with ed25519
+ I propose that proposal 220's section on authenticating with ed25519
keys be amended accordingly:
- TYPE is a different constant string, different from the one above.
+ TYPE is a different constant string, "AUTH0003".
TLSSECRETS is replaced by the output of the Exporter function in
RFC5705, using as its inputs:
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits