BBN has created three ASN.1 code generators over time and even released a 
couple. (ASN.1 to C, C++, and Java). I believe that DER to support typical 
X.509 management is the easiest subset.  I can check on status for release to 
open source if there is interest. It has been available as part of Certificate 
Management systems we've released to open source but obviously this is a very 
small COI indeed.

I can read hex dumps of ASN.1 and choose not to develop similar skills for XML 
and other types.   I'm getting too old for that kind of skill acquisition to be 
fun. But to forward reference in this chain (with apologies), I too would 
prefer a standard that that has Postel's principles as a touchstone. 

John Lowry

Sent from my iPhone

On Sep 30, 2013, at 0:28, "James A. Donald" <> wrote:

> On 2013-09-29 23:13, Jerry Leichter wrote:
>> BTW, the *idea* behind DER isn't inherently bad - but the way it ended up is 
>> another story.  For a comparison, look at the encodings Knuth came up with 
>> in the TeX world.  Both dvi and pk files are extremely compact binary 
>> representations - but correct encoders and decoders for them are plentiful.
> DER is unintelligble and incomprehensible.  There is, however, an open source 
> complier for ASN.1
> Does it not produce correct encoders and decoders for DER?  (I have never 
> used it)
> _______________________________________________
> The cryptography mailing list

Attachment: smime.p7s
Description: S/MIME cryptographic signature

The cryptography mailing list

Reply via email to