RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Currently libvirt has code to initialize libgcrypt, as a pre-requisite to using gnutls. As a result libvirt also explicitly links to -lgcrypt.

In gnutls 3.x libgcrypt is replaced by libnettle. Libvirt's explicit initialization of libgcrypt is thus bogus and is causing libvirt to link to two crypto libraries (gcrypt + nettle).

Libvirt's libgcrypt init code should be made conditional so we don't use it when gnutls is linked to nettle.

Version-Release number of selected component (if applicable):
libvirt-1.0.4-1.el7

How reproducible:
Always

Steps to Reproduce:
1. $ ldd /lib64/libvirt.so.0 | grep gcrypt
2.
3.
  
Actual results:
	libgcrypt.so.11 => /lib64/libgcrypt.so.11 (0x0000003441800000)

Expected results:
Does not link to gcrypt

Additional info:

Upstream patch proposed:
https://www.redhat.com/archives/libvir-list/2013-July/msg01687.html

v3 of upstream patch; missed 1.1.1 so it will need a backport
https://www.redhat.com/archives/libvir-list/2013-July/msg01952.html

In POST:
http://post-office.corp.redhat.com/archives/rhvirt-patches/2013-August/msg00544.html

Reproduce this bug with 
libvirt.x86_64 0:1.1.1-2.el7 

# ldd /lib64/libvirt.so.0 | grep gcrypt 
	libgcrypt.so.11 => /lib64/libgcrypt.so.11 (0x00007fde15f48000)


Verify this bug with 
libvirt.x86_64 0:1.1.1-3.el7 


[root@localhost 111-3]# ldd /lib64/libvirt.so.0 | grep gcrypt 
[root@localhost 111-3]#

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.