Is there a technical reason why we cannot use fully hardened builds for the X servers? They are currently not built as PIE, do not use BIND_NOW, and lack full RELRO as well. If there is no X-specific technical reason, but just a difficulty to get the proper build flags, I'm willing to make adjustments to redhat-rpm-config to make this easier. More information about RPM macros to set CFLAGS and LDFLAGS is available here: https://src.fedoraproject.org/rpms/redhat-rpm-config/blob/master/f/buildflags.md
(In reply to Florian Weimer from comment #0) > Is there a technical reason why we cannot use fully hardened builds for the > X servers? Yes, some of the modules it builds can't work with RTLD_NOW. For example the server dlopen's the modesetting driver, which itself dlopens the glamor acceleration code, but then calls the glamor functions by name (instead of indirecting through dlsym). With RTLD_NOW the glamor functions would be undefined and dlopen would fail. Not all of the ELF objects in the xserver build have this problem. The vbe, shadow, glamor, and exa modules, as well as basically all video drivers, depend on symbols provided by other modules. shadow glamor and exa could be fixed by linking fb into the server, which isn't the worst idea ever anyway. vbe and int10 could be linked as a unit, there's not any other module consuming int10 directly, it's always there for vbe services. Fixing the drivers would be decent amount of work though.
This bug appears to have been reported against 'rawhide' during the Fedora 28 development cycle. Changing version to '28'.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.