Jean-Marc, Nelson,
Nelson B wrote:
Jean-Marc,
Julien should really answer this question, because he's the author of the newer QuickDER decoder. But here's what I recall.
After writing QuickDER, I wrote a technote about the use of the decoders, which is at http://www.mozilla.org/projects/security/pki/nss/tech-notes/tn1.html .
In fact, my guessing is that this incompatibility refers mostly about things like breaking OCTET STRING in several parts that must be reattached together when decoding, and the possibility of outputing an element with no explicit length at the start, but an end of element marker at the end.
Right. The quick DER decoder does not decode indefinite length encoding of any type. I believe it also does not decode constructed primitive types (which you described above as an OCTET STRING in several parts). I think those are the only major restrictions.
Yes, these are the main limitations I'm aware of in the area of BER vs DER that are supported by the "classic" decoder but not by QuickDER . This information should probably be added to the technote .
_______________________________________________
mozilla-crypto mailing list
[email protected]
http://mail.mozilla.org/listinfo/mozilla-crypto
