Description of problem: During an SELinux-relabeler, I noticed this warning: filespec_add: conflicting specifications for /usr/sbin/sln and /usr/sbin/ldconfig, using system_u:object_r:ldconfig_exec_t:s0 I interpret this as a defect in glibc's SELinux rule set. Version-Release number of selected component (if applicable): glibc-2.24-4.fc25.x86_64 Additional info: The conflict also seems to show, * when running restorecon several times: # restorecon -v -r /usr/sbin restorecon reset /usr/sbin/ldconfig context system_u:object_r:bin_t:s0->system_u:object_r:ldconfig_exec_t:s0 restorecon reset /usr/sbin/sln context system_u:object_r:ldconfig_exec_t:s0->system_u:object_r:bin_t:s0 ... # restorecon -v -r /usr/sbin restorecon reset /usr/sbin/ldconfig context system_u:object_r:bin_t:s0->system_u:object_r:ldconfig_exec_t:s0 restorecon reset /usr/sbin/sln context system_u:object_r:ldconfig_exec_t:s0->system_u:object_r:bin_t:s0 ... Apparently, these 2 files get relabeled each time anew, because restorecon doesn't relabel them correctly: # restorecon -v -r /usr/sbin restorecon reset /usr/sbin/ldconfig context system_u:object_r:bin_t:s0->system_u:object_r:ldconfig_exec_t:s0 restorecon reset /usr/sbin/sln context system_u:object_r:ldconfig_exec_t:s0->system_u:object_r:bin_t:s0 # ls -lZ /usr/sbin/ldconfig /usr/sbin/sln -rwxr-xr-x. 2 root root system_u:object_r:bin_t:s0 1092984 Dec 24 02:03 /usr/sbin/ldconfig -rwxr-xr-x. 2 root root system_u:object_r:bin_t:s0 1092984 Dec 24 02:03 /usr/sbin/sln
ldconfig and sln a hard-linked and therefore need to have the same SELinux policy. It is unclear to me why ldconfig has a special policy at all. ldconfig is trusted by design, and it could easily break the system security policy by altering the way the dynamic linker behaves.
Looks like a duplicate of Bug 1378323.
This has been a bug since forever. Still a bug with Fedora 26. selinux-policy-3.13.1-260.4.fc26.noarch
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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.
*** This bug has been marked as a duplicate of bug 1460264 ***