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

2008-11-24 Thread Przemek Michalski
Max, Glad you reached to the bottom of the problem. In my case - after carefully analyzing the e_chil.c engine initialization code and my own application code - it turned out to be an extremely trivial issue. The disable_mutex_callbacks is by default initialized to 0, thus if you do not

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

2008-11-21 Thread Przemek Michalski
Max, Hi David, that is really nice.. although.. after I gave it a try... it does not really work :( Actually, it seems that the dynamic functions are never called... :( Investigating... Later, Max It seems, that indeed the dynamic locking functions are not doing the trick here. I have

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

2008-11-21 Thread Przemek Michalski
Have observed a similar problem despite the fact the nCipher patch is applied and crypto locks (both static and dynamic) are set. Have never properly investigated it so perhaps now is the time... I checked this with two versions of OpenSSL 0.9.8h (without nCipher patch and with the patch). BTW

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

2008-11-21 Thread Przemek Michalski
Sander, /opt/nfast/toolkits/openssl/openssl098e-patch.txt Could you send/post the nCipher patch 0.9.8e - I am using one supplied originally by nCipher for 0.9.8a Although the patch I have works well with all 0.9.8x versions I would be keen to compare them just for my own curiosity. thanks,

SHA-1 Broken

2005-02-18 Thread Przemek Michalski
Hi there, Anyone heard the recent news on breaking the SHA-1 hashing algorithm? I guess this is not yet official and God only knows if it is true, however what impact would this fact have on the SHA-1/RSA digital certificate signature technology in overall look. Any comments? You may view