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

[Sander Temme]

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

The problem is that they are not called by the nCipher driver - no sign

at all in the logs... :( How come they are not called ???

S.

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

Can you set a breakpoint in engines/e_chil.c:581 and inspect the value of disable_mutex_callbacks? It should be 0 and if it isn't, libnfhwcrhk never learns about the existence of the locks.

smime.p7s
Description: S/MIME cryptographic signature