Well actually I consider apps/*.c being the best openssl book :) I never really ran into any crazy stuff with openssl, which I consider to be pretty clear. The MUTEX initialization was the only real unexpected thing I ever ran into, considering the number of times its used, I logically (I guess) considered that libcrypto was in charge to initialize it. I should have double-checked.
Frédéric Giudicelli http://www.newpki.org ----- Original Message ----- From: "Joseph Bruni" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Tuesday, January 06, 2004 3:51 AM Subject: Re: OpenSSL: threading question An excellent reference to OpenSSL programming can be found in the O'Reilly book: http://www.oreilly.com/catalog/openssl/index.html Lot's of really good stuff here about common mistakes (like not initializing mutexes...). The book was written for 0.9.6 with a few references to some features in 0.9.7, but most of it should still be current. I highly recommend it considering the current state of the man pages. On Jan 5, 2004, at 1:08 PM, Frédéric Giudicelli wrote: > I just learned a few weeks ago that libcrypto and libssl did not > initialize > the MUTEX functions used internally, the application had to do it by > itself. > I guess (never really checked) my segfault problem was coming from > there > (see CRYPTO_set_locking_callback, CRYPTO_set_dynlock_create_callback, > CRYPTO_set_dynlock_lock_callback, and > CRYPTO_set_dynlock_destroy_callback). ______________________________________________________________________ OpenSSL Project http://www.openssl.org User Support Mailing List [EMAIL PROTECTED] Automated List Manager [EMAIL PROTECTED]
