Description of problem: SELinux is preventing pkla-check-auth from read access on the file /etc/authselect/nsswitch.conf. ***** Plugin restorecon (99.5 confidence) suggests ************************ If you want to fix the label. /etc/authselect/nsswitch.conf default label should be etc_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 /etc/authselect/nsswitch.conf ***** Plugin catchall (1.49 confidence) suggests ************************** If you believe that pkla-check-auth should be allowed read access on the nsswitch.conf file 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 'pkla-check-auth' --raw | audit2allow -M my-pklacheckauth # semodule -X 300 -i my-pklacheckauth.pp Additional Information: Source Context system_u:system_r:policykit_auth_t:s0 Target Context system_u:object_r:unlabeled_t:s0 Target Objects /etc/authselect/nsswitch.conf [ file ] Source pkla-check-auth Source Path pkla-check-auth Port <Unknown> Host localhost.localdomain Source RPM Packages Target RPM Packages Policy RPM selinux-policy-3.14.1-37.fc28.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name localhost.localdomain Platform Linux localhost.localdomain 4.17.9-200.fc28.x86_64 #1 SMP Mon Jul 23 21:41:29 UTC 2018 x86_64 x86_64 Alert Count 429 First Seen 2018-08-03 10:05:20 EEST Last Seen 2018-08-04 10:51:07 EEST Local ID 14b42149-494e-4544-8445-4dcebd677840 Raw Audit Messages type=AVC msg=audit(1533369067.364:1960): avc: denied { read } for pid=15663 comm="pkla-check-auth" name="nsswitch.conf" dev="loop1" ino=818 scontext=system_u:system_r:policykit_auth_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=0 Hash: pkla-check-auth,policykit_auth_t,unlabeled_t,file,read Version-Release number of selected component (if applicable): How reproducible: every now and then Steps to Reproduce: 1. use the desktop 2. 3. Actual results: selinux alerts caused by snapd appear https://i.imgur.com/tSiiKLg.png Expected results: selinux alerts caused by snapd do not appear Additional info: [asus@localhost ~]$ grep /etc/authselect/nsswitch.conf /proc/mounts /dev/loop1 /etc/authselect/nsswitch.conf squashfs ro,seclabel,nodev,relatime 0 0 [asus@localhost ~]$ losetup /dev/loop1 /dev/loop1: []: (/var/lib/snapd/snaps/core_4917.snap) [asus@localhost ~]$ sudo blockdev --getro /dev/loop1 1
1596753 may also be related
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.