Description of problem: SELinux is preventing /usr/libexec/goa-daemon from 'read' accesses on the key . ***** Plugin catchall (100. confidence) suggests ************************** If you believe that goa-daemon should be allowed read access on the key 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 goa-daemon /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context unconfined_u:unconfined_r:sandbox_x_client_t:s0:c7 51,c799 Target Context unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1 023 Target Objects [ key ] Source goa-daemon Source Path /usr/libexec/goa-daemon Port <Unknown> Host (removed) Source RPM Packages gnome-online-accounts-3.10.2-1.fc20.x86_64 Target RPM Packages Policy RPM selinux-policy-3.12.1-122.fc20.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 3.13.3-201.fc20.x86_64 #1 SMP Fri Feb 14 19:08:32 UTC 2014 x86_64 x86_64 Alert Count 3324 First Seen 2014-02-23 19:44:45 IST Last Seen 2014-02-24 00:04:55 IST Local ID a91f4be0-9456-4046-9497-b0eb5c5f6f94 Raw Audit Messages type=AVC msg=audit(1393180495.717:139252): avc: denied { read } for pid=6190 comm="pool" scontext=unconfined_u:unconfined_r:sandbox_x_client_t:s0:c751,c799 tcontext=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023 tclass=key type=SYSCALL msg=audit(1393180495.717:139252): arch=x86_64 syscall=keyctl success=yes exit=EINTR a0=b a1=33d18374 a2=7fa62403d240 a3=4 items=0 ppid=1 pid=6190 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 ses=253 tty=(none) comm=pool exe=/usr/libexec/goa-daemon subj=unconfined_u:unconfined_r:sandbox_x_client_t:s0:c751,c799 key=(null) Hash: goa-daemon,sandbox_x_client_t,unconfined_t,key,read Additional info: reporter: libreport-2.1.12 hashmarkername: setroubleshoot kernel: 3.13.3-201.fc20.x86_64 type: libreport
Are you running a gnome session?
*** Bug 1069077 has been marked as a duplicate of this bug. ***
*** Bug 1069078 has been marked as a duplicate of this bug. ***
(In reply to Miroslav Grepl from comment #1) > Are you running a gnome session? Yes.
The question is whether we should allow the sandbox access to the kernel keyring. Probably contains kerberos credentials. I am thinking no.
commit 939481da5bf2d246db1d6e097c34a76d195da548 adds dontaudit for this.
selinux-policy-3.12.1-135.fc20 has been submitted as an update for Fedora 20. https://admin.fedoraproject.org/updates/selinux-policy-3.12.1-135.fc20
Package selinux-policy-3.12.1-135.fc20: * should fix your issue, * was pushed to the Fedora 20 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.12.1-135.fc20' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2014-3813/selinux-policy-3.12.1-135.fc20 then log in and leave karma (feedback).
selinux-policy-3.12.1-135.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.