) CertFreeCertificateContext(certContext);
return m_sigvalidated;
}
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sascha Kiefer
Sent: Dienstag, 1. Mai 2007 11:02
To: openssl-dev@openssl.org
Subject: RE: OCSP Response Signature
Maybe i figured it out
@openssl.org
Subject: RE: OCSP Response Signature
Thanks for the hint.
I found out that i looked at the right signature value.
The only difference is that my signature starts with '00'H
(it always does).
Looking at the actually OCSP binary response shows me that
this '00'H is really part
PROTECTED] On Behalf Of Dr. Stephen Henson
Sent: Freitag, 27. April 2007 20:36
To: openssl-dev@openssl.org
Subject: Re: OCSP Response Signature
On Fri, Apr 27, 2007, Sascha Kiefer wrote:
Thanks for your response.
Please see the other mail i wrote in response.
The one that has the complete
What do you mean it's not ASN.1? Raw bytes with no tag? Then what's the
1st byte?
Max
Sascha Kiefer wrote:
Hello,
This is not directly related to OpenSSL, but more to OCSP in general.
I wrote my own ASN.1 Parser and doing my own crypthography using MS
CryptAPI.
I wrote my own OCSP client.
@openssl.org
Subject: Re: OCSP Response Signature
What do you mean it's not ASN.1? Raw bytes with no tag? Then
what's the 1st byte?
Max
Sascha Kiefer wrote:
Hello,
This is not directly related to OpenSSL, but more to OCSP
in general.
I wrote my own ASN.1 Parser and doing my own
On Fri, Apr 27, 2007, Sascha Kiefer wrote:
Thanks for your response.
Please see the other mail i wrote in response.
The one that has the complete ocsp response dump.
You should be able to use the OpenSSL ocsp utility to test that stuff,
including (with a debugger or printf) the expected
To make it more clear, i run the request again, but this time
I attach the original ocsp output.
Please find the part which i thing is the actual signature:
eCrypt: OCSP Response Summary:
eCrypt: --
eCrypt: Response Version: 1
eCrypt: Response Status: Successful (0)
