Description of problem: Alert popped up when installing the sendmail package. SELinux is preventing sss_cache from 'write' accesses on the directory /var/lib/sss/db. ***** Plugin catchall (100. confidence) suggests ************************** If you believe that sss_cache should be allowed write access on the db 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 'sss_cache' --raw | audit2allow -M my-ssscache # semodule -X 300 -i my-ssscache.pp Additional Information: Source Context unconfined_u:unconfined_r:useradd_t:s0-s0:c0.c1023 Target Context system_u:object_r:sssd_var_lib_t:s0 Target Objects /var/lib/sss/db [ dir ] Source sss_cache Source Path sss_cache Port <Unknown> Host (removed) Source RPM Packages Target RPM Packages sssd-common-1.16.3-2.fc28.x86_64 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.7-200.fc28.x86_64 #1 SMP Wed Dec 5 22:47:13 UTC 2018 x86_64 x86_64 Alert Count 4 First Seen 2018-12-13 21:27:05 CST Last Seen 2018-12-13 21:27:05 CST Local ID 3fe555bb-32bf-41e4-ab15-3b2c6d76a221 Raw Audit Messages type=AVC msg=audit(1544758025.454:551): avc: denied { write } for pid=27846 comm="sss_cache" name="db" dev="dm-0" ino=922503 scontext=unconfined_u:unconfined_r:useradd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:sssd_var_lib_t:s0 tclass=dir permissive=0 Hash: sss_cache,useradd_t,sssd_var_lib_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.7-200.fc28.x86_64 type: libreport
commit d7e7fe57077889f2cf4c9220cbf4a06d2d264b9b (HEAD -> rawhide, origin/rawhide) Author: Lukas Vrabec <lvrabec> Date: Tue Jan 8 18:04:41 2019 +0100 Allow ipsec_t domain dbus chat with systemd_resolved_t BZ(1662443)
*** This bug has been marked as a duplicate of bug 1658015 ***