> `pkinit_decode_data':
> pkinit_crypto_openssl.c:(.text+0x75ea): undefined reference to
> `EVP_PKEY_decrypt_old'
>
> I take this to mean that it is still not using the correct openssl?
Not necessarily, though it's hard to say without seeing the actual
call to the linker.
> Is there a target for x86_64 with icc? I could not find one in the
> Configure script, therefore I assume icc is not supported, or is it?
Try creating your own, base it off the linux-ia64-icc and the linux-x86_64
If it works out fine and passes make test submit a patch, please.
i
-
"cc:-O::(unknown)::",
>
> What would be an equivalent generic configuration for 64 bit?
If you are on Linux system, that would be:
./Configure linux-x86_64
> Best,
> Misha
i
--
Igor Galić
Tel: +43 (
SL, why not use something like
curl for the POST?
i
--
Igor Galić
Tel: +43 (0) 664 886 22 883
Mail: i.ga...@brainsware.org
URL: http://brainsware.org/
__
OpenSSL Project http://www.openssl
u'll need to know.
> Benix.
i
--
Igor Galić
Tel: +43 (0) 664 886 22 883
Mail: i.ga...@brainsware.org
URL: http://brainsware.org/
__
OpenSSL Project http://www.openssl.org
User
the same result as a valid path.
> There are also problems with various other programs, which can't do
> verification...
>
> Any cure known? Something more to specify here?
None of which I would know, or RT:
http://rt.openssl.org/Ticket/Display.html?id=977&user=guest&pa
crashes because of ssleay32.dll from OpenSSL 1.0.0c)
Can you provide a trace of the crash?
What do your certificates look like?
i
--
Igor Galić
Tel: +43 (0) 664 886 22 883
Mail: i.ga...@brainsware.org
URL: http://brainsware.org/
_