[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

[tor-commits] [torspec/master] dir-spec: Specify linewrapping behaviour for base64-encoded data.



commit 8ebdf2e99f93628055c7d7a89327191cf4d161dc
Author: Isis Lovecruft <isis@xxxxxxxxxxxxxx>
Date:   Tue Aug 1 17:15:21 2017 +0000

    dir-spec: Specify linewrapping behaviour for base64-encoded data.
    
     * THANKS TO Mr. George Costanza for pointing out the ambiguity.
---
 dir-spec.txt | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/dir-spec.txt b/dir-spec.txt
index c3f9563..ec0b2ab 100644
--- a/dir-spec.txt
+++ b/dir-spec.txt
@@ -201,8 +201,12 @@
   Objects. A KeywordLine begins with a Keyword, optionally followed by
   whitespace and more non-newline characters, and ends with a newline.  A
   Keyword is a sequence of one or more characters in the set [A-Za-z0-9-].
-  An Object is a block of encoded data in pseudo-Open-PGP-style
-  armor. (cf. RFC 2440)
+  An Object is a block of encoded data in pseudo-Privacy-Enhanced-Mail (PEM)
+  style format: that is, lines of encoded data MAY be wrapped by inserting
+  an ascii linefeed ("LF", also called newline, or "NL" here) character
+  (cf. RFC 4648 §3.1).  When line wrapping, implementations MUST wrap lines
+  at 64 characters.  Upon decoding, implementations MUST ignore and discard
+  all linefeed characters.
 
   More formally:
 



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