On 05/26/2011 02:06 PM, Clint Adams wrote:
> On Mon, May 03, 2010 at 03:55:21AM -0700, Howard Chu wrote:
>> Anyway, probably the first step for GnuTLS is to add a new init API
>> that also initializes gcrypt threading, so that apps do all of their
>> interaction solely with GnuTLS, instead of havin
On Mon, May 03, 2010 at 03:55:21AM -0700, Howard Chu wrote:
> Anyway, probably the first step for GnuTLS is to add a new init API
> that also initializes gcrypt threading, so that apps do all of their
> interaction solely with GnuTLS, instead of having to also use gcrypt
> init APIs and hope they a
Simon Josefsson wrote:
Howard Chu writes:
App writers using gnutls should not need to know that libgcrypt is
under the covers and needs special handling.
The Libgcrypt designers appears to have believed otherwise, and given
how broken the applications appear to be in this area decision (setui
Simon Josefsson wrote:
Howard Chu writes:
None of the gnutls docs mention that any special initialization
function needs to be called when using it in a threaded application.
You must have missed this section:
http://www.gnu.org/software/gnutls/manual/html_node/Multi_002dthreaded-application
Howard Chu writes:
>> See comment #72 of this launchpad bug report for a detailed description
>> of why libgcrypts behavior causes the problem in libldap.
>>
>> https://bugs.launchpad.net/debian/+source/sudo/+bug/423252/
>> https://bugs.launchpad.net/debian/+source/sudo/+bug/423252/comments/72
>
See comment #72 of this launchpad bug report for a detailed description
of why libgcrypts behavior causes the problem in libldap.
https://bugs.launchpad.net/debian/+source/sudo/+bug/423252/
https://bugs.launchpad.net/debian/+source/sudo/+bug/423252/comments/72
Note that the root cause here is t
6 matches
Mail list logo
