Created attachment 620239 [details] avcs in permissive mode $ id -Z staff_u:staff_r:staff_t:s0-s0:c0.c1023 $ rpm -q kgpg kgpg-4.9.1-1.fc18.x86_64 $ rpm -q selinux-policy selinux-policy-3.11.1-25.fc18.noarch $ LC_ALL=C kgpg unnamed app(6935): KUniqueApplication: Cannot find the D-Bus session server: "Failed to connect to socket /tmp/dbus-sDp5CJoM5L: Permission denied" unnamed app(6934): KUniqueApplication: Pipe closed unexpectedly.
kgpg is X-window application and it's run with gpg_t. I think it's not necessary. I've tried to change context of /usr/bin/kgpg to bin_t and it seems to work. It looks like that kgpg uses gpg2 and type transistion should be done when kgpg runs /usr/bin/gpg2.
The question is why we have this label.
Should probably leave /usr/bin/kgpg bin_t. It will domain type transition as soon as it runs gpg(2)?
Removing it and see if we get an AVC about it. Fixed in selinux-policy-3.11.1-37.fc18.noarch
selinux-policy-3.11.1-43.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/selinux-policy-3.11.1-43.fc18
selinux-policy-3.11.1-46.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/selinux-policy-3.11.1-46.fc18
Package selinux-policy-3.11.1-46.fc18: * should fix your issue, * was pushed to the Fedora 18 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.11.1-46.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16862/selinux-policy-3.11.1-46.fc18 then log in and leave karma (feedback).
selinux-policy-3.11.1-46.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
knemo wont start unnamed app(7067): KUniqueApplication: Pipe closed unexpectedly unnamed app(7068): KUniqueApplication: Cannot find the D-Bus session server: "Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken."