Hide Forgot
Description of problem: SELinux is preventing ldconfig from 'write' accesses on the fifo_file /var/tmp/dracut.oKVM2b/systemd-cat. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that ldconfig should be allowed write access on the systemd-cat fifo_file by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'ldconfig' --raw | audit2allow -M my-ldconfig # semodule -X 300 -i my-ldconfig.pp Additional Information: Source Context system_u:system_r:ldconfig_t:s0 Target Context system_u:object_r:initrc_tmp_t:s0 Target Objects /var/tmp/dracut.oKVM2b/systemd-cat [ fifo_file ] Source ldconfig Source Path ldconfig Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.13.1-191.18.fc24.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.7.7-200.fc24.x86_64 #1 SMP Sat Oct 8 00:21:59 UTC 2016 x86_64 x86_64 Alert Count 7 First Seen 2016-10-07 10:33:36 EDT Last Seen 2016-10-24 10:28:46 EDT Local ID 90fc0de1-ce7f-4586-a799-b9f2052fa210 Raw Audit Messages type=AVC msg=audit(1477319326.384:187): avc: denied { write } for pid=1877 comm="ldconfig" path="/var/tmp/dracut.oKVM2b/systemd-cat" dev="dm-0" ino=914428 scontext=system_u:system_r:ldconfig_t:s0 tcontext=system_u:object_r:initrc_tmp_t:s0 tclass=fifo_file permissive=0 Hash: ldconfig,ldconfig_t,initrc_tmp_t,fifo_file,write Version-Release number of selected component: selinux-policy-3.13.1-191.18.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.7.7-200.fc24.x86_64 type: libreport
Looks like leaked file descriptors.
(In reply to Daniel Walsh from comment #1) > Looks like leaked file descriptors. No. That is on purpose logging the output to the journal with systemd-cat.
If we expect lots of tools to be able to write to this tmp file we need to label it with something all domains can write to. Or we just write a policy that says all domains can get inherited write perms to initrc_tmp_t. init_rw_inherited_script_tmp_files(domain) Or better would be to write a new interface that allows only write, no read init_write_inherited_script_tmp_files(domain)
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. 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 '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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.