Summary: SELinux is preventing /bin/plymouth "search" access on /etc/libvirt/qemu. Detailed Description: SELinux denied access requested by plymouth. It is not expected that this access is required by plymouth and this access may signal an intrusion attempt. It is also possible that the specific version or configuration of the application is causing it to require additional access. Allowing Access: You can generate a local policy module to allow this access - see FAQ (http://docs.fedoraproject.org/selinux-faq-fc5/#id2961385) Please file a bug report. Additional Information: Source Context unconfined_u:system_r:plymouth_t:s0 Target Context system_u:object_r:virt_etc_rw_t:s0 Target Objects /etc/libvirt/qemu [ dir ] Source plymouth Source Path /bin/plymouth Port <Unknown> Host (removed) Source RPM Packages plymouth-0.8.0-0.2009.29.09.19.3.fc12 Target RPM Packages libvirt-0.7.1-15.fc12 Policy RPM selinux-policy-3.6.32-84.fc12 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Plugin Name catchall Host Name (removed) Platform Linux (removed) 2.6.31.12-174.2.3.fc12.x86_64 #1 SMP Mon Jan 18 19:52:07 UTC 2010 x86_64 x86_64 Alert Count 2 First Seen Fri 19 Feb 2010 03:59:16 PM CET Last Seen Fri 19 Feb 2010 04:01:33 PM CET Local ID f127774b-a8ae-49c3-9bf0-63ba73edfc31 Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1266591693.562:8350): avc: denied { search } for pid=11303 comm="plymouth" name="qemu" dev=dm-0 ino=98438 scontext=unconfined_u:system_r:plymouth_t:s0 tcontext=system_u:object_r:virt_etc_rw_t:s0 tclass=dir node=(removed) type=SYSCALL msg=audit(1266591693.562:8350): arch=c000003e syscall=2 success=no exit=-2 a0=405563 a1=0 a2=18 a3=18 items=0 ppid=11297 pid=11303 auid=500 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=pts12 ses=1 comm="plymouth" exe="/bin/plymouth" subj=unconfined_u:system_r:plymouth_t:s0 key=(null) Hash String generated from catchall,plymouth,plymouth_t,virt_etc_rw_t,dir,search audit2allow suggests: #============= plymouth_t ============== allow plymouth_t virt_etc_rw_t:dir search;
Why is plymouth executing qemu?
it doesn't. Not that I know of anyway. /bin/plymouth does have a command line argument that makes it run the passed in command (for feeding passwords to programs during boot up). It could be something in the virt stack is running it, although that seems unlikely.
Robert how did you get this to happen?
I honestly don't know. I was going through SELinux security alerts cleaning them up and noticed this one. I thought it was odd and that it could do with reporting. I normally work with KVM virt, bringing up machines and down again quite regularly, creating snapshots and kickstarting. I just checked and I didn't reboot at that time, nor did I log in. There also were no RPM updates on the 19th. Logs from around that time from /var/log: [root@hostname log]# pwd /var/log [root@hostname log]# grep -ri 'Feb 19 03:5' * cron-20100221:Feb 19 03:50:01 hostname CROND[1459]: (root) CMD (/usr/lib64/sa/sa1 -S DISK 1 1) [root@hostname log]# grep -ri 'Feb 19 04:1' * cron-20100221:Feb 19 04:10:01 hostname CROND[3265]: (root) CMD (/usr/lib64/sa/sa1 -S DISK 1 1) messages-20100221:Feb 19 04:14:05 hostname afpd[3586]: ASIP session:548(5) from 192.168.178.24:58176(7) messages-20100221:Feb 19 04:14:05 hostname afpd[2694]: server_child[1] 3586 done messages-20100221:Feb 19 04:14:05 hostname afpd[3588]: ASIP session:548(5) from 192.168.178.24:58177(7) messages-20100221:Feb 19 04:14:05 hostname afpd[2694]: server_child[1] 3588 done messages-20100221:Feb 19 04:14:06 hostname afpd[3589]: ASIP session:548(5) from 192.168.178.24:58178(7) messages-20100221:Feb 19 04:14:06 hostname afpd[3590]: ASIP session:548(5) from 192.168.178.24:58179(7) messages-20100221:Feb 19 04:14:06 hostname afpd[2694]: server_child[1] 3589 done messages-20100221:Feb 19 04:14:06 hostname afpd[2694]: server_child[1] 3590 done messages-20100221:Feb 19 04:14:08 hostname afpd[3597]: ASIP session:548(5) from 192.168.178.24:58181(7) messages-20100221:Feb 19 04:14:08 hostname afpd[2694]: server_child[1] 3597 done messages-20100221:Feb 19 04:14:08 hostname afpd[3598]: ASIP session:548(5) from 192.168.178.24:58182(7) messages-20100221:Feb 19 04:14:08 hostname afpd[2694]: server_child[1] 3598 done messages-20100221:Feb 19 04:14:08 hostname afpd[3599]: ASIP session:548(5) from 192.168.178.24:58183(7) messages-20100221:Feb 19 04:14:08 hostname afpd[2694]: server_child[1] 3599 done messages-20100221:Feb 19 04:14:08 hostname afpd[3600]: ASIP session:548(5) from 192.168.178.24:58184(7) messages-20100221:Feb 19 04:14:08 hostname afpd[2694]: server_child[1] 3600 done messages-20100221:Feb 19 04:14:46 hostname afpd[3650]: ASIP session:548(5) from 192.168.178.24:58187(7) messages-20100221:Feb 19 04:14:46 hostname afpd[2694]: server_child[1] 3650 done messages-20100221:Feb 19 04:14:46 hostname afpd[3651]: ASIP session:548(5) from 192.168.178.24:58188(7) messages-20100221:Feb 19 04:14:46 hostname afpd[2694]: server_child[1] 3651 done messages-20100221:Feb 19 04:14:46 hostname afpd[3652]: ASIP session:548(5) from 192.168.178.24:58189(7) messages-20100221:Feb 19 04:14:46 hostname afpd[3653]: ASIP session:548(5) from 192.168.178.24:58190(7) messages-20100221:Feb 19 04:14:46 hostname afpd[2694]: server_child[1] 3652 done messages-20100221:Feb 19 04:14:46 hostname afpd[2694]: server_child[1] 3653 done messages-20100221:Feb 19 04:14:46 hostname afpd[3655]: ASIP session:548(5) from 192.168.178.24:58191(7) messages-20100221:Feb 19 04:14:46 hostname afpd[2694]: server_child[1] 3655 done messages-20100221:Feb 19 04:14:46 hostname afpd[3656]: ASIP session:548(5) from 192.168.178.24:58192(7) messages-20100221:Feb 19 04:14:46 hostname afpd[2694]: server_child[1] 3656 done messages-20100221:Feb 19 04:14:46 hostname afpd[3657]: ASIP session:548(5) from 192.168.178.24:58193(7) messages-20100221:Feb 19 04:14:46 hostname afpd[2694]: server_child[1] 3657 done messages-20100221:Feb 19 04:14:46 hostname afpd[3658]: ASIP session:548(5) from 192.168.178.24:58194(7) messages-20100221:Feb 19 04:14:46 hostname afpd[2694]: server_child[1] 3658 done So I'm baffled as to what would cause this. I'm more than happy to run any tests if you like me to?
Do you run lots of virtual machines? Ray does plymouth only run on shutdown? Or does it run on suspend? Could plymouth execute a bunch of scripts that could notify virtual machines to suspend?
Usually one or two constantly and then I fire up and reboot/re-provision between 2 - 5 a day..
AFAIK, nothing in libvirt / virtualization stack calls into Plymouth. Nor can I think of why plymouth would need to directly access any of the files under /etc/libvirt/qemu directly - indeed we explicitly tell apps never todo that, only use the libvirt APIs.
Is /etc/libvirt/qemu a mountpoint?
No, /etc/libvirt/qemu is not a mountpoint.
Are you still seeing this problem. Lost in the flood of bugs.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 WONTFIX if it remains open with a Fedora 'version' of '12'. 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 prior to Fedora 12's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 12 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 please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. 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. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days