Description of problem: This is one of a cascade of related reports presented each morning after I open my laptop. SELinux is preventing certwatch from 'write' accesses on the directory /boot/efi. ***** Plugin restorecon (99.5 confidence) suggests ************************ If you want to fix the label. /boot/efi default label should be boot_t. Then you can run restorecon. The access attempt may have been stopped due to insufficient permissions to access a parent directory in which case try to change the following command accordingly. Do # /sbin/restorecon -v /boot/efi ***** Plugin catchall (1.49 confidence) suggests ************************** If you believe that certwatch should be allowed write access on the efi 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:dosfs_t:s0 Target Objects /boot/efi [ dir ] Source certwatch Source Path certwatch Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages Policy RPM <Unknown> Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.19.4-300.fc29.x86_64 #1 SMP Fri Nov 23 13:03:11 UTC 2018 x86_64 x86_64 Alert Count 128 First Seen 2018-11-26 08:56:37 AEST Last Seen 2018-12-03 10:08:38 AEST Local ID 75ddcb54-68ff-4966-927e-fe663b2a939e Raw Audit Messages type=AVC msg=audit(1543795718.635:10532): avc: denied { write } for pid=22300 comm="certwatch" name="/" dev="sda1" ino=1 scontext=system_u:system_r:certwatch_t:s0-s0:c0.c1023 tcontext=system_u:object_r:dosfs_t:s0 tclass=dir permissive=0 Hash: certwatch,certwatch_t,dosfs_t,dir,write Additional info: component: selinux-policy reporter: libreport-2.9.6 hashmarkername: setroubleshoot kernel: 4.19.4-300.fc29.x86_64 type: libreport
*** This bug has been marked as a duplicate of bug 1655357 ***