Hi,
I have implemented the static callbacks provided by OpenSSL for thread
safety issue.
After implementing the callback the performance of my program degraded
drartically
since this callback is issued from lot of places while accepting a new
connection.
This callback is issued nearly 200 times fr
Lock your app data separately from the lock that OpenSSL uses to
protect its own stuff. Don't manipulate the OpenSSL structures
directly, though if you've got reason to lock your application data
you can include the OpenSSL structures in your own locking.
lock(appdata)
(call into openssl)
Hi,
Thanks for your input. AFAIK registering these callbacks will result
in locking the SSL datastructures internally by the OpenSSL whenever
required. My question is since I've handled these in my application is
it necessay for me to register these callbacks once again to the
OpenSSL. I'm handlin
Hi,
I think you needn't lock the SSL_connect/SSL_accept. It's too low efficient.
You just have to set the lock callback using:
CRYPTO_set_locking_callback(pthread_lock_handler);
CRYPTO_set_id_callback(id_handler);
It works fine in linux. But it does not in WinXP. I was puzzled with
