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

2008-11-28 Thread Geoff Thorpe
On Friday 21 November 2008 14:50:41 Sander Temme wrote: [snip] I would suggest a documentation fix, like so: Index: engines/e_chil.c === RCS file: /home/openssl/cvs/openssl/engines/e_chil.c,v retrieving revision 1.9 diff -u

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

2008-11-24 Thread Przemek Michalski
be generated. A patch with a single error line would do the trick here I think. Thanks, P.M. - Original Message - From: Max Pala [EMAIL PROTECTED] To: OpenSSL Users openssl-users@openssl.org Sent: Friday, November 21, 2008 8:41 PM Subject: FIXED - CRYPTO_set_dynlock_* mystery ... (was: Engine

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

2008-11-22 Thread Massimiliano Pala
Hi Sander, I debugged the init process and it seems that you were right. The disable_mutex_callbacks is set to 1 at e_chil.c:578. Definitely it is due to initialization, at this point... ... looked into that, and... et voilas! Found the problem! The PRE commands were wrong. Indeed the

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

2008-11-22 Thread Massimiliano Pala
Hi Geoff, that would be amazing.. I agree with you.. if there were more hours in the day... hehehe... The patch from Sanders looks ok to me... :D It can actually help in understanding better the option... Later, Max Geoff Thorpe wrote: As I stated in another post, I'm looking to overhaul the

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

2008-11-21 Thread Max Pala
Hi Sander, I debugged the init process and it seems that you were right. The disable_mutex_callbacks is set to 1 at e_chil.c:578. Definitely it is due to initialization, at this point... ... looked into that, and... et voilas! Found the problem! The PRE commands were wrong. Indeed the

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

2008-11-21 Thread Sander Temme
On Nov 21, 2008, at 11:12 AM, Massimiliano Pala wrote: Hi Sander, I debugged the init process and it seems that you were right. The disable_mutex_callbacks is set to 1 at e_chil.c:578. Definitely it is due to initialization, at this point... ... looked into that, and... et voilas! Found the

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

2008-11-21 Thread Geoff Thorpe
On Friday 21 November 2008 14:41:08 Max Pala wrote: Hi Sander, I debugged the init process and it seems that you were right. The disable_mutex_callbacks is set to 1 at e_chil.c:578. Definitely it is due to initialization, at this point... ... looked into that, and... et voilas! Found the