Hide Forgot
SELinux is preventing /usr/bin/gnome-keyring-daemon from using the 'setcap' accesses on a process. ***** Plugin catchall (100. confidence) suggests *************************** If you believe that gnome-keyring-daemon should be allowed setcap access on processes labeled user_gkeyringd_t 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 gnome-keyring-d /var/log/audit/audit.log | audit2allow -M mypol # semodule -i mypol.pp Additional Information: Source Context user_u:user_r:user_gkeyringd_t:s0 Target Context user_u:user_r:user_gkeyringd_t:s0 Target Objects Unknown [ process ] Source gnome-keyring-d Source Path /usr/bin/gnome-keyring-daemon Port <Unknown> Host (removed) Source RPM Packages gnome-keyring-3.0.3-1.fc15 Target RPM Packages Policy RPM selinux-policy-3.9.16-26.fc15 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name (removed) Platform Linux (removed) 2.6.38.7-30.fc15.x86_64 #1 SMP Fri May 27 05:15:53 UTC 2011 x86_64 x86_64 Alert Count 4 First Seen Mo 13 Jun 2011 12:20:43 CEST Last Seen Mo 13 Jun 2011 12:20:44 CEST Local ID 4868b719-32b2-494c-b3ca-36e9663a1460 Raw Audit Messages type=AVC msg=audit(1307960444.370:361): avc: denied { setcap } for pid=5846 comm="gnome-keyring-d" scontext=user_u:user_r:user_gkeyringd_t:s0 tcontext=user_u:user_r:user_gkeyringd_t:s0 tclass=process type=SYSCALL msg=audit(1307960444.370:361): arch=x86_64 syscall=capset success=no exit=EACCES a0=7f8a3eec87d4 a1=7f8a3eec87dc a2=1 a3=0 items=0 ppid=5693 pid=5846 auid=502 uid=502 gid=502 euid=502 suid=502 fsuid=502 egid=502 sgid=502 fsgid=502 tty=(none) ses=20 comm=gnome-keyring-d exe=/usr/bin/gnome-keyring-daemon subj=user_u:user_r:user_gkeyringd_t:s0 key=(null) Hash: gnome-keyring-d,user_gkeyringd_t,user_gkeyringd_t,process,setcap audit2allow #============= user_gkeyringd_t ============== allow user_gkeyringd_t self:process setcap; audit2allow -R #============= user_gkeyringd_t ============== allow user_gkeyringd_t self:process setcap;
this is in master branch i should i guess by applied to f15. by the way there also a mod to allow gkeyringd to read system state that we may want to add to f15
Fixed in selinux-policy-3.9.16-29.fc15
selinux-policy-3.10.0-118.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/selinux-policy-3.10.0-118.fc17
Package selinux-policy-3.10.0-118.fc17: * should fix your issue, * was pushed to the Fedora 17 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.10.0-118.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-6452/selinux-policy-3.10.0-118.fc17 then log in and leave karma (feedback).
selinux-policy-3.10.0-118.fc17 has been pushed to the Fedora 17 stable repository. If problems still persist, please make note of it in this bug report.