> Well now I think of it that isn't actually sufficient. You need to add
> B_ASN1_NUMERICSTRING to the ored values for B_ASN1_PRINTABLE in
> crypto/asn1/asn1.h too.
>
It works (just checked) and it is nicer. Forget mine fix, use yours.
__
>
> Do you have a sample certificate using that other string type?
>
Mailing list doesn't allow to send attachments, so you can get it here
-- http://vrghost.lv/~vrghost/vr.test.key.CRT.zip
openssl executable fails when said
openssl x509 -in vr.test.key.CRT -noout -text -fingerprint -inform DER
On Wed, Jan 28, 2009, Dr. Stephen Henson wrote:
> On Tue, Jan 27, 2009, Ilya O. wrote:
>
> > Hello.
> >
> > I've discovered that openssl (at least 0.9.8j and 0.9.8i) fails po
> > parse certificate if it has PostalCode encoded as NumericString (and
> > this is allowed thing according to RFC3280).
On Tue, Jan 27, 2009, Ilya O. wrote:
> Hello.
>
> I've discovered that openssl (at least 0.9.8j and 0.9.8i) fails po
> parse certificate if it has PostalCode encoded as NumericString (and
> this is allowed thing according to RFC3280).
>
> The error log reads following
> {{{
> unable to load cert
Hello.
I've discovered that openssl (at least 0.9.8j and 0.9.8i) fails po
parse certificate if it has PostalCode encoded as NumericString (and
this is allowed thing according to RFC3280).
The error log reads following
{{{
unable to load certificate
3664:error:0D07808C:asn1 encoding routines:ASN1_
