Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionDaniel Berrangé
2013-09-10 12:07:04 UTC
Description of problem:
It is a goal for libvirt in RHEL-7 to have full RELRO hardening. Unfortunately we missed this for the loadable modules, per this upstream commit
commit f1f0e53b0814aab3c093f1219da95c0f836cdf4a
Author: Guido Günther <agx>
Date: Sun Sep 1 08:50:58 2013 +0200
Pass AM_LDFLAGS to driver modules too
This gives us a RO got, otherwise Debian's lintian complains:
W: libvirt-bin: hardening-no-relro usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so
W: libvirt-bin: hardening-no-relro usr/lib/libvirt/connection-driver/libvirt_driver_storage.so
W: libvirt-bin: hardening-no-relro usr/lib/libvirt/connection-driver/libvirt_driver_uml.so
W: libvirt-bin: hardening-no-relro usr/lib/libvirt/connection-driver/libvirt_driver_vbox.so
W: libvirt-bin: hardening-no-relro usr/lib/libvirt/connection-driver/libvirt_driver_xen.so
W: libvirt-bin: hardening-no-relro usr/lib/libvirt/connection-driver/libvirt_driver_nwfilter.so
W: libvirt-bin: hardening-no-relro usr/lib/libvirt/connection-driver/libvirt_driver_storage.so
W: libvirt-bin: hardening-no-relro usr/lib/libvirt/connection-driver/libvirt_driver_uml.so
W: libvirt-sanlock: hardening-no-relro usr/lib/libvirt/lock-driver/sanlock.so
Version-Release number of selected component (if applicable):
libvirt-1.1.1-4.el7
How reproducible:
Always
Steps to Reproduce:
1. Use 'eu-readelf -a' to look for the 'BIND_NOW' flag on every .so file in the libvirt RPMs
2.
3.
Actual results:
$ eu-readelf -a /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so | grep BIND_NOW
Expected results:
$ eu-readelf -a /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so | grep BIND_NOW
BIND_NOW
Additional info:
Hi Jiri ,
I found both -4 version which don't have the patch and -12 version that don't have key word BIND_NOW but GNU_RELRO .
Is there a another way to prove that those file have full RELRO hardening ?
I upload the log of the command
#eu-readelf -a /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so
with latest libvirt
Jiri , could you provide a command line with rpmdiff to reproduce the hardening-no-relro warning on rhel ?
I try to used lintian , but found there is no libvirt-1.1.1-4-bin any more on debians side , seems like they don't keep those old unstable package.
BTW , libvirt-1.2.0-bin passed without warning via lintian.
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.
Description of problem: It is a goal for libvirt in RHEL-7 to have full RELRO hardening. Unfortunately we missed this for the loadable modules, per this upstream commit commit f1f0e53b0814aab3c093f1219da95c0f836cdf4a Author: Guido Günther <agx> Date: Sun Sep 1 08:50:58 2013 +0200 Pass AM_LDFLAGS to driver modules too This gives us a RO got, otherwise Debian's lintian complains: W: libvirt-bin: hardening-no-relro usr/lib/libvirt/connection-driver/libvirt_driver_qemu.so W: libvirt-bin: hardening-no-relro usr/lib/libvirt/connection-driver/libvirt_driver_storage.so W: libvirt-bin: hardening-no-relro usr/lib/libvirt/connection-driver/libvirt_driver_uml.so W: libvirt-bin: hardening-no-relro usr/lib/libvirt/connection-driver/libvirt_driver_vbox.so W: libvirt-bin: hardening-no-relro usr/lib/libvirt/connection-driver/libvirt_driver_xen.so W: libvirt-bin: hardening-no-relro usr/lib/libvirt/connection-driver/libvirt_driver_nwfilter.so W: libvirt-bin: hardening-no-relro usr/lib/libvirt/connection-driver/libvirt_driver_storage.so W: libvirt-bin: hardening-no-relro usr/lib/libvirt/connection-driver/libvirt_driver_uml.so W: libvirt-sanlock: hardening-no-relro usr/lib/libvirt/lock-driver/sanlock.so Version-Release number of selected component (if applicable): libvirt-1.1.1-4.el7 How reproducible: Always Steps to Reproduce: 1. Use 'eu-readelf -a' to look for the 'BIND_NOW' flag on every .so file in the libvirt RPMs 2. 3. Actual results: $ eu-readelf -a /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so | grep BIND_NOW Expected results: $ eu-readelf -a /usr/lib64/libvirt/connection-driver/libvirt_driver_qemu.so | grep BIND_NOW BIND_NOW Additional info: