> 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. B
l Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Kingston
Smiler
Sent: Wednesday, September 05, 2007 3:53 PM
To: openssl-users@openssl.org
Subject: Reagrding Thread safety in OpenSSL
Hi,
I'm having a small query regarding the thread safety of the
OpenSSL libra
] On Behalf Of Kingston Smiler
> >Sent: Wednesday, September 05, 2007 3:53 PM
> >To: openssl-users@openssl.org
> >Subject: Reagrding Thread safety in OpenSSL
> >
> >Hi,
> > I'm having a small query regarding the thread safety of the
> >OpenSSL library.
s puzzled with it
too.
Regards,
Kurt.
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of Kingston Smiler
>Sent: Wednesday, September 05, 2007 3:53 PM
>To: openssl-users@openssl.org
>Subject: Reagrding Thread safety in OpenSSL
>
&g
Hi,
I'm having a small query regarding the thread safety of the OpenSSL library.
OpenSSL provide some set of Static Locking Callbacks and Dynamic
locking callbacks to ensure the thread safety of the OpenSSL data
structures. But if the application using the OpenSSL, implements its
own locking me