Summary: SELinux is preventing /usr/bin/mono "read write" access on sdb2. Detailed Description: SELinux denied access requested by mono. It is not expected that this access is required by mono 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://fedora.redhat.com/docs/selinux-faq-fc5/#id2961385) Please file a bug report. Additional Information: Source Context system_u:system_r:podsleuth_t:s0 Target Context system_u:object_r:fixed_disk_device_t:s0 Target Objects sdb2 [ blk_file ] Source mono Source Path /usr/bin/mono Port <Unknown> Host (removed) Source RPM Packages mono-core-2.4.2.3-2.fc12 Target RPM Packages Policy RPM selinux-policy-3.6.32-69.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.i686 #1 SMP Mon Jan 18 20:22:46 UTC 2010 i686 i686 Alert Count 8 First Seen Fri 22 Jan 2010 10:52:15 AM PST Last Seen Fri 22 Jan 2010 05:05:19 PM PST Local ID 0c6cc50a-86a4-4608-9f37-8ed6d74fb082 Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1264208719.928:21498): avc: denied { read write } for pid=2319 comm="mono" name="sdb2" dev=tmpfs ino=55991 scontext=system_u:system_r:podsleuth_t:s0 tcontext=system_u:object_r:fixed_disk_device_t:s0 tclass=blk_file node=(removed) type=SYSCALL msg=audit(1264208719.928:21498): arch=40000003 syscall=5 per=400000 success=no exit=-13 a0=976cbb8 a1=8002 a2=0 a3=0 items=0 ppid=2311 pid=2319 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="mono" exe="/usr/bin/mono" subj=system_u:system_r:podsleuth_t:s0 key=(null) Hash String generated from selinux-policy-3.6.32-69.fc12,catchall,mono,podsleuth_t,fixed_disk_device_t,blk_file,read,write audit2allow suggests: #============= podsleuth_t ============== allow podsleuth_t fixed_disk_device_t:blk_file { read write };
*** This bug has been marked as a duplicate of bug 544659 ***