Description of problem: SELinux is preventing /usr/share/syst from 'write' accesses on the directory /etc/selinux. ***** Plugin selinuxpolicy (91.4 confidence) suggests ********************* If you do not think syst should try write access on selinux. Then you may be under attack by a hacker, since confined applications should not need this access. Do contact your security administrator and report this issue. ***** Plugin catchall (9.59 confidence) suggests ************************** If you believe that syst 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: # grep /usr/share/syst /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context staff_u:staff_r:staff_t:s0 Target Context system_u:object_r:selinux_config_t:s0 Target Objects /etc/selinux [ dir ] Source /usr/share/syst Source Path /usr/share/syst Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages libsemanage-2.3-6.fc21.x86_64 selinux- policy-3.13.1-82.fc21.noarch Policy RPM selinux-policy-3.13.1-82.fc21.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.16.3-300.fc21.x86_64 #1 SMP Wed Sep 17 20:54:02 UTC 2014 x86_64 x86_64 Alert Count 1 First Seen 2014-09-20 08:13:41 PDT Last Seen 2014-09-20 08:13:41 PDT Local ID 8843d994-ff6b-4e75-a809-17d7275717fc Raw Audit Messages type=AVC msg=audit(1411226021.935:1012): avc: denied { write } for pid=6506 comm="/usr/share/syst" name="selinux" dev="dm-0" ino=392 scontext=staff_u:staff_r:staff_t:s0 tcontext=system_u:object_r:selinux_config_t:s0 tclass=dir permissive=0 Hash: /usr/share/syst,staff_t,selinux_config_t,dir,write Version-Release number of selected component: selinux-policy-3.13.1-82.fc21.noarch Additional info: reporter: libreport-2.2.3 hashmarkername: setroubleshoot kernel: 3.16.3-300.fc21.x86_64 type: libreport
*** This bug has been marked as a duplicate of bug 1144762 ***