[tor-commits] [torspec/master] Correct an error in proposal 224 citing 220

nickm at torproject.org nickm at torproject.org
Wed Sep 7 00:12:45 UTC 2016


commit 3cc0e9b3a82435404f00036bd11b33689cc98080
Author: Nick Mathewson <nickm at torproject.org>
Date:   Tue Sep 6 20:12:40 2016 -0400

    Correct an error in proposal 224 citing 220
---
 proposals/224-rend-spec-ng.txt | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/proposals/224-rend-spec-ng.txt b/proposals/224-rend-spec-ng.txt
index 6cbdc9b..bf2bfe6 100644
--- a/proposals/224-rend-spec-ng.txt
+++ b/proposals/224-rend-spec-ng.txt
@@ -1044,9 +1044,10 @@ Table of contents:
           appendix A. The certificate type must be [10], and the signing-key
           extension is mandatory.
 
-          For "legacy" keys, certificate is a proposal 220 certificate wrapped
-          in "-----BEGIN CROSSCERT-----" armor, cross-certifying the
-          descriptor signing key with the legacy RSA encryption key.
+          For "legacy" keys, certificate is a proposal 220 RSA->Ed
+          cross-certificate wrapped in "-----BEGIN CROSSCERT-----" armor,
+          cross-certifying the descriptor signing key with the legacy RSA
+          encryption key.
 
    To remain compatible with future revisions to the descriptor format,
    clients should ignore unrecognized lines in the descriptor.



More information about the tor-commits mailing list