[xmlsec] Thread safety?

[Erwann ABALEA]

Bonjour,

Hodie XVIII Kal. Ian. MMV est, Aleksey Sanin scripsit:
> Hm.. I have a strange feeling that I already answered on *exactly* the
> same question:
> 
> http://www.aleksey.com/pipermail/xmlsec/2003/000546.html

The answer is not complete. The crypto libraries don't only need to be
compiled with threads support, some code has to be added. For
example, OpenSSL requires the application to call the
CRYPTO_set_id_callback() and CRYPTO_set_locking_callback() functions
with the right arguments. If you don't do it, OpenSSL can't safely be
used in a multithreaded program.

> Deja vu?
> 
> Aleksey
> 
> Kenny Chamber wrote:
> >I'm considering using XMLSec in a multi-threaded environment. Is libxmlsec
> >thread-safe? I gather from the archives and bug database that libxslt is 
> >not
> >thread-safe, so libxmlsec would need to guard calls into libxslt. That's
> >hardly an ideal situation, and I'd be surprised if you've done it.
> >
> >Assuming that libxmlsec is not presently thread-safe, are the issues
> >entirely in the libraries it uses, or are there issues in libxmlsec itself?

-- 
Erwann ABALEA <erwann.abalea at keynectis.com>