I'm using HPUX 11.23, Itanium, openssl-0.9.8d, cc 6.10
I seem to have found a contradiction in the build environment and I
don't think it is specific to HPUX, but rather to platforms who have a
64bit 'long long' and require a %ll to print them.
What we want to build is a 32bit binary build
Here is the included Make Reprot as understood the term...
-
$ make
making all in crypto...
make[1]: Entering directory
`/export/users/akulkarni/dwnlods/openssl-0.9.8d/crypto'
( echo #ifndef
That seems to be a bug with openssl dev package, as I am trying to build
on a native ppc64 machine why should it add a -b directive asking for a
cross-compilation machine. Please note my code compiles without it
though!
If there is any specific reason that I am missing please let me know.
Atul Kulkarni (SIGSEC) via RT wrote:
That seems to be a bug with openssl dev package, as I am trying to build
on a native ppc64 machine why should it add a -b directive asking for a
cross-compilation machine. Please note my code compiles without it
though!
If there is any specific reason
If I am cross-certifying a root cert with another root cert, and both
roots are in my cert store, then OpenSSL might see an ambiguous chain
when it tries to verify. There would be two possible chains instead of
one. Can OpenSSL handle such a case? I haven't found any documentation
on this. Thanks,
On Thu, Jan 11, 2007, Andrews, Rick wrote:
If I am cross-certifying a root cert with another root cert, and both
roots are in my cert store, then OpenSSL might see an ambiguous chain
when it tries to verify. There would be two possible chains instead of
one. Can OpenSSL handle such a case? I
When requesting ocsp service, by both -url https, or by -host -port,
the latest openssl crashes with a segment fault under win32.
Report attached.ÿþ ? x m l v e r s i o n = 1 . 0 e n c o d i n g = U T F - 1 6 ?
D A T A B A S E
E X E N A M E = o p e n s s l . e x e
Arrakis wrote:
When requesting ocsp service, by both -url https, or by -host -port,
the latest openssl crashes with a segment fault under win32.
Could you try a recent snapshot (of 0.9.8-stable or the head) ?
As far as I remember I fixed something concerning the SSL_CTX
initialization some
Thanks, but that doesn't completely answer my question. Let me rephrase:
As OpenSSL is walking up the chain, it looks at a cert's issuer name and
then tries to find a cert in the cert store with that name as a subject
name. In my case, it will find two. Does it just pick the first one (if
so, I
I would be pleased to test it if windows binaries are supplied with
development signature.
Regards,
Arrakis
Arrakis wrote:
When requesting ocsp service, by both -url https, or by -host -port,
the latest openssl crashes with a segment fault under win32.
Could you try a recent snapshot (of
On Thu, Jan 11, 2007, Andrews, Rick wrote:
Thanks, but that doesn't completely answer my question. Let me rephrase:
As OpenSSL is walking up the chain, it looks at a cert's issuer name and
then tries to find a cert in the cert store with that name as a subject
name. In my case, it will find
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
12 matches
Mail list logo
