[7591] in cryptography@c2.net mail archive
Re: tool for conversion between certificate encoding
daemon@ATHENA.MIT.EDU (Donald E. Eastlake 3rd)
Fri Jul 28 01:52:26 2000
Message-Id: <200007280215.WAA22273@torque.pothole.com>
To: snaik@oblix.com
Cc: cryptography@c2.net
In-reply-to: Your message of "Thu, 27 Jul 2000 14:43:04 EDT."
<398082B8.2E1EED43@oblix.com>
Date: Thu, 27 Jul 2000 22:15:26 -0400
From: "Donald E. Eastlake 3rd" <dee3@torque.pothole.com>
What are you really trying to do? X.509 is ASN.1 encoded by
definition and that is important because it's that encoding that is
signed. I can understand wanting to part a certificate and extract
fields, but why would you generally want to convert it to a different
encoding? For anyone to verify it, they would have to convert back
to ASN.1 DER ...
Donald
From: Sanket Naik <snaik@oblix.com>
Message-ID: <398082B8.2E1EED43@oblix.com>
Date: Thu, 27 Jul 2000 14:43:04 -0400
Organization: Oblix Inc
To: cryptography@c2.net
>hi
>
>can someone point me to a tool (preferably unix command line) for
>conversion between different X.509 certificate encodings, DER, base64,
>....
>
>thanks
>sanket
