[Pkg-libvirt-maintainers] Bug#745946: gtk-vnc: Uses gcrypt functions without explicit gcrypt build-dependency

[Andreas Metzler]

Package: gtk-vnc
Version: 0.5.2-3
Severity: normal
User: ametzler at debian.org
Usertags: gnutls3

gtk-vnc uses gcrypt directly (not only as an indirect dependency
via gnutls) but does not build-depend on it.

Some of the code (thread handler) would probably superfluous
nowadays[1] for the other functions it might be better to switch from
gcrypt to gnutls' crypto API, to limit external depencies. (GnuTLS v3
uses nettle instead of gcrypt.)

cu Andreas


[1]
------------------------------
NEWS in gnutls 2.12
** 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
------------------------------
 
-- 
`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'