Feedback - cryptosphere/ordo GitHub Wiki

Via @CodesInChaos:

Q: What linebreak characters?

A: CRLF. Always. Bare CRs or LFs are wrong.

Q: Better hashing semantics? (preprocess and remove "wrap at 64" prior to hashing)

A: The goal is to produce canonical documents without ambiguities, and if they contain any ambiguities, they are wrong and should be rejected by the parser. If we have a truly canonical document, no transformations should be needed on it prior to hashing.

Q: Character encoding? Escape characters? \0?

A: We can adventurously specify UTF-8 as the encoding for ORDO certificates, although US-ASCII would be a more conservative choice. ORDO provides no escaping mechanisms, however uses the URI Generic Syntax which does. \0 is expressly disallowed by all ORDO documents and should be rejected by the parser.

Q: ordo.dn does not conform to URI generic syntax

A: This should be fixed everywhere. Let me know if you spot a place using invalid syntax.

Q: Can you have spaces in values?

A: It would be nice if this weren't necessary. We will presume no for now, but perhaps add support if a field which needs them arises.

Q: Basic constraint stuff: What about critical extensions?

A much bigger can of worms. TBD.