> I am currently working on a project making use of SSL
> connections via OpenSSL. We need a stable thread-safe
> SSL setup. I currently know 3 things about OpenSSL
> thread-safety:
>
> 1. Cannot share SSL connection amongst threads
> 2. Provide locking_function()
> 3. Provide id_function()
Write wrappers around the malloc/free functions to use shared memory,
to share objects among threads.
Hunh?
The whole point of threads is that they share the same address space, so
you don't need shared memory. You might/do need locking, depending on
what you're doing.
/r$
--
Rich
Hi,
I would say openssl is not thread-safe per se, but you can deal with it.
Write wrappers around the malloc/free functions to use shared memory,
to share objects among threads. Write thread-safe functions around the
ssl functions you need to access from multiple threads ...
For example code, op
I am currently working on a project making use of SSL
connections via OpenSSL. We need a stable thread-safe
SSL setup. I currently know 3 things about OpenSSL
thread-safety:
1. Cannot share SSL connection amongst threads
2. Provide locking_function()
3. Provide id_function()
I am interested in