Re: CRYPTO_set_dynlock_* mystery ... (was: Engine Issue: nShield 500)

[Sander Temme]

On Nov 21, 2008, at 8:07 AM, Max Pala wrote:

I definitely did - now I do initialize all the static locks in OpenSSL *and* the dynamic functions. But they are never called by the chil - the assert fails and

the SIGABRT is sent to my daemon forcing it to exit.

The library needs both the static locks and the dynamic locking upcalls.

Anybody knows where can I find the patched OpenSSL version from nCipher ?

/opt/nfast/toolkits/openssl/openssl098e-patch.txt





S.

--
[EMAIL PROTECTED]              http://www.temme.net/sander/
PGP FP: 51B4 8727 466A 0BC3 69F4  B7B8 B2BE BC40 1529 24AF

Should apply cleanly to newer versions of OpenSSL, with patch -p1. It creates a static lock for CHIL to use so it doesn't need the dynamic ones available. I personally think the dynamic locking concept is more elegant, but I do agree it smells of duplicated code because everyone has to set up the same scaffolding.

smime.p7s
Description: S/MIME cryptographic signature