Hide Forgot
libreport version: 2.0.8 executable: /usr/bin/python hashmarkername: setroubleshoot kernel: 3.2.2-1.fc16.x86_64 reason: SELinux is preventing /usr/lib/virtualbox/VBoxManage from 'execute_no_trans' accesses on the None /usr/lib/virtualbox/VBoxManage. time: Sun 29 Jan 2012 07:11:22 PM EST description: :SELinux is preventing /usr/lib/virtualbox/VBoxManage from 'execute_no_trans' accesses on the None /usr/lib/virtualbox/VBoxManage. : :***** Plugin catchall (100. confidence) suggests *************************** : :If you believe that VBoxManage should be allowed execute_no_trans access on the VBoxManage <Unknown> 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 VBoxManage /var/log/audit/audit.log | audit2allow -M mypol :# semodule -i mypol.pp : :Additional Information: :Source Context system_u:system_r:boinc_t:s0 :Target Context system_u:object_r:textrel_shlib_t:s0 :Target Objects /usr/lib/virtualbox/VBoxManage [ None ] :Source VBoxManage :Source Path /usr/lib/virtualbox/VBoxManage :Port <Unknown> :Host (removed) :Source RPM Packages VirtualBox-4.1-4.1.8_75467_fedora16-1.x86_64 :Target RPM Packages VirtualBox-4.1-4.1.8_75467_fedora16-1.x86_64 :Policy RPM selinux-policy-3.10.0-72.fc16.noarch :Selinux Enabled True :Policy Type targeted :Enforcing Mode Permissive :Host Name (removed) :Platform Linux (removed) 3.2.2-1.fc16.x86_64 #1 : SMP Thu Jan 26 03:21:58 UTC 2012 x86_64 x86_64 :Alert Count 5 :First Seen Sun 29 Jan 2012 01:40:25 PM EST :Last Seen Sun 29 Jan 2012 07:10:29 PM EST :Local ID 512a09bc-0934-49f5-b8a3-9e8bbf23f616 : :Raw Audit Messages :type=AVC msg=audit(1327882229.103:79): avc: denied { execute_no_trans } for pid=2303 comm="sh" path="/usr/lib/virtualbox/VBoxManage" dev=dm-1 ino=1972867 scontext=system_u:system_r:boinc_t:s0 tcontext=system_u:object_r:textrel_shlib_t:s0 tclass=filenode=(removed) type=SYSCALL msg=audit(1327882229.103:79): arch=c000003e syscall=59 success=yes exit=0 a0=1440eb0 a1=1440230 a2=143fe70 a3=18 items=0 ppid=2296 pid=2303 auid=4294967295 uid=993 gid=990 euid=993 suid=993 fsuid=993 egid=990 sgid=990 fsgid=990 tty=(none) ses=4294967295 comm="VBoxManage" exe="/usr/lib/virtualbox/VBoxManage" subj=system_u:system_r:boinc_t:s0 key=(null) : : :Hash: VBoxManage,boinc_t,textrel_shlib_t,None,execute_no_trans : :audit2allow : : :audit2allow -R : :
Did you change the label for /usr/lib/virtualbox/VBoxManage? $ matchpathcon /usr/lib/virtualbox/VBoxManage /usr/lib/virtualbox/VBoxManage system_u:object_r:bin_t:s0 Are you able to find an alert which suggested you. What does $ matchpathcon /usr/lib/virtualbox/VBoxManage for you?
The matchpathcon returns "/usr/lib/virtualbox/VBoxManage system_u:object_r:bin_t:s" as you thought. After further oberservation it seems to be triggered by not actually using Virtual Box, but starting boinc-client. I can use service start, then service stop, then service start and keep recreating the message. Will watch today, but believe it only happens when the boinc-client is started. Anything else just let me know. I have been using "setenforce 0" to test since this start after the last update. Thanks, Devon
Devon run restorecon on the executable and once it is bin_t the AVC will no longer happen.
$ restorecon -v /usr/lib/virtualbox/VBoxManage
Tested what you wrote and seemed to correct the problem. Can you provide any insite or a link for me to read as to why this goes sideways? Thanks, Devon