RE: Need help: Understanding SSL object in multi-threaded environment

Kyle, Thanks for your long and detailed response. OpenSSL can protect its internal state by employing locks on the things that are interface-opaque. It cannot protect its transparent state, especially as things other than OpenSSL that just happen to know how the interface works may not use

Re: Need help: Understanding SSL object in multi-threaded environment

On 10/6/06, Mark [EMAIL PROTECTED] wrote: David, I assume this a reason why OpenSSL has the locking callback functions. No. OpenSSL has the locking callback functions so it can protect internal structures. For example, if two SSL objects internally reference the objects. I am still

RE: Need help: Understanding SSL object in multi-threaded environment

David, I assume this a reason why OpenSSL has the locking callback functions. No. OpenSSL has the locking callback functions so it can protect internal structures. For example, if two SSL objects internally reference the objects. I am still confused as to why the locking callbacks

RE: Need help: Understanding SSL object in multi-threaded environment

David, I'm not sure why more internal details of how OpenSSL works would be helpful. I've already explained the external interface. I think it would be helpful for me. If we need to prevent calling SSL functions on the same object (i.e. SSL_read() and SSL_write()) from different threads then

Re: Need help: Understanding SSL object in multi-threaded environment

Mark wrote: I think it would be helpful for me. If we need to prevent calling SSL functions on the same object (i.e. SSL_read() and SSL_write()) from different threads then I would think that OpenSSL would not need any internal synchronisation, unless it creates its own threads internally.

RE: Need help: Understanding SSL object in multi-threaded environment

Darryl, But the SSL_() API set is not re-entrant with respect of the same SSL * handle. So you have to serialize all API calls upon the same SSL * handle. This is why you can't mix SSL_read() with any other SSL_() API call on the same handle instance at the same time. I think

Re: Need help: Understanding SSL object in multi-threaded environment

- Original Message - From: Darryl Miles [EMAIL PROTECTED] To: openssl-users@openssl.org Sent: Friday, October 06, 2006 4:50 PM Subject: Re: Need help: Understanding SSL object in multi-threaded environment Mark wrote: I think it would be helpful for me. If we need to prevent

RE: Need help: Understanding SSL object in multi-threaded environment

David, I assume this a reason why OpenSSL has the locking callback functions. No. OpenSSL has the locking callback functions so it can protect internal structures. For example, if two SSL objects internally reference the objects. I am still confused as to why the locking

Need help: Understanding SSL object in multi-threaded environment

Hi all, I have some doubts about openssl and multithreaded environment. I will appreciate if you could help me understand this better. It is said that openssl is thread-safe with a limitation that "an SSL connection may not concurrently be used by multiple threads" I am not clear on this

RE: Need help: Understanding SSL object in multi-threaded environment

H_SSL. HTH André From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Urjit GokhaleSent: Donnerstag, 5. Oktober 2006 09:33To: openssl-users@openssl.orgSubject: Need help: Understanding SSL object in multi-threaded environment Hi all, I have some doubts about openssl and multithreaded

RE: Need help: Understanding SSL object in multi-threaded environment

you may use the same H_SSL_CTX (handle to an SSL context) in concurrent threads. This structure serves as a factory of ssl connections. You use SSL_new to create SSL connection handles (H_SSL). These you can use only within one thread. So, you may share H_SSL_CTX, you may not share

Re: Need help: Understanding SSL object in multi-threaded environment

- Original Message - From: Mark [EMAIL PROTECTED] To: openssl-users@openssl.org Sent: Thursday, October 05, 2006 2:49 PM Subject: RE: Need help: Understanding SSL object in multi-threaded environment you may use the same H_SSL_CTX (handle to an SSL context) in concurrent threads

RE: Need help: Understanding SSL object in multi-threaded environment

1. Is OpenSSL thread-safe? Yes (with limitations: an SSL connection may not concurrently be used by multiple threads) This means exactly what it says. A single SSL connection may not be used concurrently by multiple threads. This means it is illegal for one thread to do a 'write' on the

RE: Need help: Understanding SSL object in multi-threaded environment

David, 1. Is OpenSSL thread-safe? Yes (with limitations: an SSL connection may not concurrently be used by multiple threads) This means exactly what it says. A single SSL connection may not be used concurrently by multiple threads. This means it is illegal for one thread to do a

RE: Need help: Understanding SSL object in multi-threaded environment

I assume this a reason why OpenSSL has the locking callback functions. No. OpenSSL has the locking callback functions so it can protect internal structures. For example, if two SSL objects internally reference the objects. As long as you use these it is safe to share the object AFAIK. Then

RE: Need help: Understanding SSL object in multi-threaded environment

Is it the case that both SSL_read and SSL_write modify the same part of the SSL object ? Yes, but that's not the issue. Could you give some more details about this? Could you throw some more light on the ssl state maintained by the SSL object during SSL_read and SSL_write? I'm not sure

RE: Need help: Understanding SSL object in multi-threaded environment

help: Understanding SSL object in multi-threaded environment David, 1. Is OpenSSL thread-safe? Yes (with limitations: an SSL connection may not concurrently be used by multiple threads) This means exactly what it says. A single SSL connection may not be used concurrently