Source: gloox
Version: 1.0.9-3
Severity: normal
User: ametz...@debian.org
Usertags: gnutls3
gloox links against libgcrypt. Afaict the only reason for this is
gnutls related:
------------------------
ametzler@argenau:/tmp/RBGNUT/gloox-1.0.9$ grep -2ri gcry src
src/tlsgnutlsclient.cpp-#ifdef HAVE_PTHREAD
src/tlsgnutlsclient.cpp-extern "C" {
src/tlsgnutlsclient.cpp:GCRY_THREAD_OPTION_PTHREAD_IMPL;
src/tlsgnutlsclient.cpp-}
src/tlsgnutlsclient.cpp-#endif
--
src/tlsgnutlsclient.cpp- const StringList&
/*cacerts*/ )
src/tlsgnutlsclient.cpp- {
src/tlsgnutlsclient.cpp: gcry_control( GCRYCTL_SET_THREAD_CBS,
&gcry_threads_pthread );
src/tlsgnutlsclient.cpp-
src/tlsgnutlsclient.cpp- const int protocolPriority[] = {
--
src/tlsgnutlsclient.h-#include <gnutls/gnutls.h>
src/tlsgnutlsclient.h-#include <gnutls/x509.h>
src/tlsgnutlsclient.h:#include <gcrypt.h>
src/tlsgnutlsclient.h-
src/tlsgnutlsclient.h-namespace gloox
------------------------
I strongly suspect that the whole code is unnecessary even with gnutls
2.11:
------------------------------
** libgnutls: Added gnutls_global_set_mutex() to allow setting
alternative locking procedures. By default the system available
locking is used. In *NIX pthreads are used and in windows the
critical section API. This follows a different approach than the
previous versions that depended on libgcrypt initialization. The
locks are now set by default in systems that support it. Programs
that used gcry_control() to set thread locks should insert it into
a block of
#if GNUTLS_VERSION_NUMBER <= 0x020b00
gcry_control(...)
#endif
------------------------------
And it is definitely not useful with gnutls3, since it uses nettle
instead of gcrypt.
Please either make linkage against libgcrypt and inclusion of
gcrypt.h conditional on usage of ancient gnutls or simply require a
not-that-ancient version of gnutls (2.12.0 was released 2011-03-24).
cu Andreas
--
`What a good friend you are to him, Dr. Maturin. His other friends are
so grateful to you.'
`I sew his ears on from time to time, sure'
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
