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.
Description of problem:
Description of problem:
The e2fsprogs package contains libraries (specifically libcomm_err). We would like them to be built with partial RELRO support as a security enhancement.
Additional info:
Partial RELRO requires these passed at link: -Wl,-z,relro
You can fix this by patching the Makefiles to add this link flag to LDFLAGS or you might be able to simply add LDFLAGS="$LDFLAGS -Wl,-z,relro" to the configure line in the rpm's spec file. You will have to test the built packages to ensure the flags are properly passed all the way to the end of build. It does not hurt anything if the package contains applications that pick up partial relro support, too.
I don't understand why this is reported as an issue 4 days before it is due to be resolved?
We have a planning phase that closed a long time ago. That is when you need to make this kind of request please!
Aside from the poor timing, can I get a little background?
What are the implications of this? Should the entire package build with
those flags? What does this fix, and why is libcom_err so special in this
regard?
Built & tagged in e2fsprogs-1.41.12-10.el6
[root@inode tmp]# ./rpm-chksec libcom_err e2fsprogs-libs libss e2fsprogs
FILE TYPE RELRO PIE
/lib64/libcom_err.so.2.1 library partial DSO
/lib64/libe2p.so.2.3 library partial DSO
/lib64/libext2fs.so.2.4 library partial DSO
/lib64/libss.so.2.0 library partial DSO
/sbin/badblocks exec partial no
/sbin/debugfs exec partial no
/sbin/dumpe2fs exec partial no
/sbin/e2fsck exec partial no
/sbin/e2image exec partial no
/sbin/e2label exec partial no
/sbin/e2undo exec partial no
/sbin/fsck.ext2 exec partial no
/sbin/fsck.ext3 exec partial no
/sbin/fsck.ext4 exec partial no
/sbin/fsck.ext4dev exec partial no
/sbin/logsave exec partial no
/sbin/mke2fs exec partial no
/sbin/mkfs.ext2 exec partial no
/sbin/mkfs.ext3 exec partial no
/sbin/mkfs.ext4 exec partial no
/sbin/mkfs.ext4dev exec partial no
/sbin/resize2fs exec partial no
/sbin/tune2fs exec partial no
/usr/bin/chattr exec partial no
/usr/bin/lsattr exec partial no
/usr/sbin/e2freefrag exec partial no
/usr/sbin/filefrag exec partial no
/usr/sbin/mklost+found exec partial no
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2011-1735.html