Description of problem: It happened without any action. SELinux is preventing snort from 'search' accesses on the directory /var/lib/sss. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that snort should be allowed search access on the sss 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 snort /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context system_u:system_r:snort_t:s0 Target Context system_u:object_r:sssd_var_lib_t:s0 Target Objects /var/lib/sss [ dir ] Source snort Source Path snort Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages sssd-common-1.13.0-4.fc22.x86_64 Policy RPM selinux-policy-3.13.1-128.16.fc22.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 4.1.10-200.fc22.x86_64 #1 SMP Mon Oct 5 14:22:49 UTC 2015 x86_64 x86_64 Alert Count 9 First Seen 2015-10-13 03:08:49 CDT Last Seen 2015-10-31 20:34:03 CDT Local ID b725d183-581c-42be-b345-46cf5583d1e5 Raw Audit Messages type=AVC msg=audit(1446341643.781:682): avc: denied { search } for pid=3628 comm="snort" name="sss" dev="dm-1" ino=2224077 scontext=system_u:system_r:snort_t:s0 tcontext=system_u:object_r:sssd_var_lib_t:s0 tclass=dir permissive=0 Hash: snort,snort_t,sssd_var_lib_t,dir,search Version-Release number of selected component: selinux-policy-3.13.1-128.16.fc22.noarch Additional info: reporter: libreport-2.6.2 hashmarkername: setroubleshoot kernel: 4.1.10-200.fc22.x86_64 type: libreport
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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.