Whether the OpenLDAP code that depends on GnuTLS is in a separate
process from the application or not, it might still need to set
Libgcrypt thread support callbacks when it initializes GnuTLS.
Werner Koch makes the point that ideally the application (nss-pam-ldapd
or whatever) would initialize Libgcrypt. Meanwhile everyone seems to
agree that a library which introduces an indirect dependency on
Libgcrypt (i.e. GnuTLS) should be failsafe and initialize Libgcrypt
itself if the application forgot to do that.
Then how should it check if the application forgot to initialize
Libgcrypt? Testing GCRYCTL_ANY_INITIALIZATION_P is consistent with
Libgcrypt documentation...
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
