Re: libgcrypt thread safety

2012-02-08 Thread Lei Zhang
On Wed, Feb 8, 2012 at 1:56 PM, Marcus Meissner wrote: > On Wed, Feb 08, 2012 at 02:48:06PM -0600, Adam Martinson wrote: >> I've been looking into bug 27036 >> , and it's due to the >> lack of thread safety by default in libgcrypt (in this case via >>

Re: libgcrypt thread safety

2012-02-08 Thread Marcus Meissner
On Wed, Feb 08, 2012 at 02:48:06PM -0600, Adam Martinson wrote: > I've been looking into bug 27036 > , and it's due to the > lack of thread safety by default in libgcrypt (in this case via > libgnutls in secur32.dll). To be thread safe, libgcrypt requ

libgcrypt thread safety

2012-02-08 Thread Adam Martinson
I've been looking into bug 27036 , and it's due to the lack of thread safety by default in libgcrypt (in this case via libgnutls in secur32.dll). To be thread safe, libgcrypt requires a call to gcry_control(GCRYCTL_SET_THREAD_CBS) before any libgc