Hello, > > Mark wrote: > > > Have you implemented the CRYPTO locking callbacks? > > > > Well, my sample code is such simple that i did not think to > > implement them. > > Nevertheless, it works really fine on ANY platform it has > > been tested, BUT under quadri Xeon Windows 2003. > > As a matter of fact, there is NO multithreading involved in my test. > > ONLY multi processing. > > As far as i understood, the crypto locking callbacks are usefull only > > when multi threading is involved. > > > > Then, do you really think the crypto locking callbacks can do > > anything for me ? > > > > Well, i'll try to extract mttest.c corresponding code to do some more > > tests ... > > I'm not an expert in OpenSSL but AFAIK OpenSSL uses threads internally > and > the locking callbacks are necessary to synchronise its internal data. > > Perhaps someone else can clarify this? OpenSSL does not use threads internally and if you don't use threads too in your program then there is no need to implement static locking callback (for example for daemon working in fork() mode).
Best regards, -- Marek Marcola <[EMAIL PROTECTED]> ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List openssl-users@openssl.org Automated List Manager [EMAIL PROTECTED]
