if(certContext != NULL) 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: OC
To: openssl-dev@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
t; From: [EMAIL PROTECTED]
> [mailto:[EMAIL 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.
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: openssl-dev@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 Op
CSP client. Everything works fine.
The only part i can not figure out, is the ocsp response signature part.
I guess, i do not have a problem with ASN.1 or the MSCAPI, but of the way
the
Signature is encoded.
Here, the sample output of my program:
eCrypt: OCSP Response Summa
e 63 ed 5e c3 aa 9d -.þcí^ê
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of Sascha Kiefer
> Sent: Donnerstag, 26. April 2007 21:11
> To: openssl-dev@openssl.org
> Subject: OCSP Response Signature
>
>
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. Everything works fine.
The only part i can not figure out, is the ocsp response signature part.
I guess, i do not
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. Everything works fine.
The only part i can not figure out, is the ocsp response signature part.
I guess, i do not
Hi,
I reported this in the 'user' forum also as 'garbage-in garbage-out' - but
not as a bug.
Looks like a BER encoded nonce in an OCSP request gets copied back in the
response - the critical flag was 'false' which is the default so should
not be encoded for DER. The signature appears to be com
10 matches
Mail list logo
