Description of problem: SELinux is preventing certwatch from 'write' accesses on the directory /sys/fs/selinux. ***** Plugin setenforce (91.4 confidence) suggests ************************ If you believe certwatch tried to disable SELinux. Then you may be under attack by a hacker, since confined applications should never need this access. Do contact your security administrator and report this issue. ***** Plugin catchall (9.59 confidence) suggests ************************** If you believe that certwatch should be allowed write access on the selinux directory 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 'certwatch' --raw | audit2allow -M my-certwatch # semodule -X 300 -i my-certwatch.pp Additional Information: Source Context system_u:system_r:certwatch_t:s0-s0:c0.c1023 Target Context system_u:object_r:security_t:s0 Target Objects /sys/fs/selinux [ dir ] Source certwatch Source Path certwatch Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.14.1-48.fc28.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.19.6-200.fc28.x86_64 #1 SMP Sun Dec 2 18:03:32 UTC 2018 x86_64 x86_64 Alert Count 36 First Seen 2018-12-12 03:11:06 EST Last Seen 2018-12-14 03:30:13 EST Local ID bd9d62a2-b66a-427f-b39e-66c43fbbb669 Raw Audit Messages type=AVC msg=audit(1544776213.932:69095): avc: denied { write } for pid=15458 comm="certwatch" name="/" dev="selinuxfs" ino=1 scontext=system_u:system_r:certwatch_t:s0-s0:c0.c1023 tcontext=system_u:object_r:security_t:s0 tclass=dir permissive=0 Hash: certwatch,certwatch_t,security_t,dir,write Version-Release number of selected component: selinux-policy-3.14.1-48.fc28.noarch Additional info: component: selinux-policy reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.19.6-200.fc28.x86_64 type: libreport Potential duplicate: bug 1653091
*** Bug 1659559 has been marked as a duplicate of this bug. ***
*** Bug 1659560 has been marked as a duplicate of this bug. ***
*** Bug 1659564 has been marked as a duplicate of this bug. ***
*** Bug 1659561 has been marked as a duplicate of this bug. ***
*** Bug 1659566 has been marked as a duplicate of this bug. ***
*** Bug 1659569 has been marked as a duplicate of this bug. ***
*** Bug 1659570 has been marked as a duplicate of this bug. ***
*** Bug 1659557 has been marked as a duplicate of this bug. ***
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.