Here is a dump.
I can see the CN - but I could see that before.
There is also a RSA - maybe a signature or maybe is the public key for the cert.
I would expect to see some signed data (sha + symantec cert + time)
and also the public cert ( and maybe the intermediaries..)
<30 82 03 AB>
0
On Fri, Apr 22, 2016, c.hol...@ades.at wrote:
> hi!
>
> I am using openssl-smime for signing outgoing messages and verifying
> incoming.
> My question is about verifying.
>
> If the partner signs a message where the certificate is included in
> the signature all is OK.
> If he signes only with
On Thu, Apr 21, 2016, Juan Sebasti?n C?rdenas Arenas wrote:
> Good Morning
>
> My name is Juan Sebastian Cardenas, I'm a Systems engineer from Colombia
>
> I am implementing an internal PKI for the organization where I work using
> openssl
>
> The idea is to generate certificates and digital
> It isn't clear from your message what the cause is. It is possible that the
> requests are using GET format which the ocsp utility doesn't support.
It does support GET in master.
--
openssl-users mailing list
To unsubscribe: https://mta.openssl.org/mailman/listinfo/openssl-users
hi!
I am using openssl-smime for signing outgoing messages and verifying
incoming.
My question is about verifying.
If the partner signs a message where the certificate is included in the
signature all is OK.
If he signes only with issuer and serial included in the signature i get
an error
