> Most definitely not. ... Yes you are right.
To qualify what I want to do: openssl does a lot of sharing and locking. I would like to use the minimum by have one context per thread. I use my own session cache so there 'should' not need to be anything else that needs sharing. Further, I use my own BIO buffers and rand object. So in my app, openssl does not go to the operating system for anything. Can you please give me some hints what I should look at changing in openssl to do this? Paul Sent via my BlackBerry from Vodacom - let your email find you! -----Original Message----- From: "David Schwartz" <[EMAIL PROTECTED]> Date: Sun, 20 Jan 2008 11:59:00 To:<openssl-dev@openssl.org> Subject: RE: Static global - bug? (Re: Two valgrind warnings in OpenSSL - possible bug???) > I should be able to create a multithreaded application using > a non-multithreaded openssl build provided that I have an ssl > context per thread. Most definitely not. At a minimum, the definition of things like 'errno' and 'malloc' might be different between a multithreaded build and a non-multithreaded build. There is no supported way to combine multithreaded code and code that was not compiled to be multithreaded. It may happen to work, but that's a lousy way to make security-sensitive software. DS ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List openssl-dev@openssl.org Automated List Manager [EMAIL PROTECTED] :§I"Ï®ÞrØm¶ÿà (¥éì²Z+7¯zZ)éí1¨¥x Ëh¥éì²W^¾^Ë%¢¸ ºÚ&j×.+-1©Úêæj:+v¨¢§²Éh®
