Hello,
I'm trying to verify an x509 certificate with a custom library (other than
openssl)
The reason I'm writing to this mailing list is that I can't figure out what
is going wrong.
The library is checked and nothing is wrong so I must be missing something.
The program I'm writing has to be
NID is an internal openssl implementation detail; X509 data structures have
OID's.
Post the PEM of the cert.
/r$
--
Principal Security Engineer
Akamai Technology
Cambridge, MA
The certificate is received in ASN.1 DER format. Not PEM.
The only thing I want to do is verify the signature of the certificate, and
thus verify the signature itself.
It is self-signed so the public key in the certificate should be used to
verify the signature, but it isn't working.
Certificate:
Hi,
I'm looking for Cryptographic Message Syntax (CMS)
Authenticated-Enveloped-Data Content Type (RFC 5083) support within
OpenSSL. Is this RFC already implemented? I just found support of pure
cms_enveloped_data in 1.0.1e.
Thanks in advance.
Markus
The point of posting PEM is that people can cut and paste from a mail message
and decode it to get the DER or whatever. (That's why PEM format was invented,
to survive intact through email:)
You are generating a certificate, self-signing it, and your recipient cannot
verify it. Right?
From: owner-openssl-users On Behalf Of Dereck Hurtubise
Sent: Wednesday, November 27, 2013 04:40
I'm trying to verify an x509 certificate with a custom library (other than
openssl)
The reason I'm writing to this mailing list is that I can't figure out what
is going wrong.
The certificate is
