Description of problem: SELinux is preventing rngd from 'execmod' accesses on the file /usr/sbin/rngd. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that rngd should be allowed execmod access on the rngd 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 'rngd' --raw | audit2allow -M my-rngd # semodule -X 300 -i my-rngd.pp Additional Information: Source Context system_u:system_r:rngd_t:s0 Target Context system_u:object_r:rngd_exec_t:s0 Target Objects /usr/sbin/rngd [ file ] Source rngd Source Path rngd Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages rng-tools-5-7.fc24.i686 Policy RPM selinux-policy-3.13.1-190.fc24.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.5.5-300.fc24.i686 #1 SMP Thu May 19 13:42:13 UTC 2016 i686 i686 Alert Count 3 First Seen 2016-07-15 20:27:45 EEST Last Seen 2016-07-16 09:59:38 EEST Local ID 5d060007-3994-4989-9607-9e2242361291 Raw Audit Messages type=AVC msg=audit(1468652378.136:80): avc: denied { execmod } for pid=755 comm="rngd" path="/usr/sbin/rngd" dev="dm-0" ino=271896 scontext=system_u:system_r:rngd_t:s0 tcontext=system_u:object_r:rngd_exec_t:s0 tclass=file permissive=0 Hash: rngd,rngd_t,rngd_exec_t,file,execmod Version-Release number of selected component: selinux-policy-3.13.1-190.fc24.noarch Additional info: reporter: libreport-2.7.2 hashmarkername: setroubleshoot kernel: 4.6.3-300.fc24.i686 type: libreport Potential duplicate: bug 1181308
*** Bug 1367152 has been marked as a duplicate of this bug. ***
*** Bug 1376225 has been marked as a duplicate of this bug. ***
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Getting this on reboot: [root@mha ~]# last -adi reboot | head -n1 reboot system boot Wed Nov 30 08:45 still running 0.0.0.0 [root@mha ~]# ausearch -m avc -ts "08:45" ---- time->Wed Nov 30 08:45:27 2016 type=AVC msg=audit(1480520727.327:86): avc: denied { execmod } for pid=756 comm="rngd" path="/usr/sbin/rngd" dev="dm-1" ino=657985 scontext=system_u:system_r:rngd_t:s0 tcontext=system_u:object_r:rngd_exec_t:s0 tclass=file permissive=0 [root@mha ~]# debugfs -R 'ncheck 657985' /dev/dm-1 debugfs 1.43.1 (08-Jun-2016) Inode Pathname 657985 /usr/sbin/rngd Running: selinux-policy-targeted-3.13.1-225.fc25.noarch selinux-policy-3.13.1-225.fc25.noarch rng-tools-5-8.fc25.i686
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.