Summary: SELinux is preventing /usr/bin/mono "read write" access on sde1. Detailed Description: [mono has a permissive type (podsleuth_t). This access was not denied.] 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 sde1 [ 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-49.fc12 Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Plugin Name catchall Host Name (removed) Platform Linux (removed) 2.6.31.6-145.fc12.x86_64 #1 SMP Sat Nov 21 15:57:45 EST 2009 x86_64 x86_64 Alert Count 2 First Seen Sat 05 Dec 2009 04:55:33 PM EST Last Seen Sat 05 Dec 2009 04:55:33 PM EST Local ID ba18cbd9-d014-4df2-b41c-2c60d484ad57 Line Numbers Raw Audit Messages node=(removed) type=AVC msg=audit(1260050133.44:29032): avc: denied { read write } for pid=29840 comm="mono" name="sde1" dev=tmpfs ino=2046729 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(1260050133.44:29032): arch=c000003e syscall=2 success=yes exit=4294967424 a0=2afce80 a1=2 a2=0 a3=d items=0 ppid=29835 pid=29840 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-49.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 };
We have to get this device labeled correctly by udev or someone. removable_t is now allowed.
This is a duplicate of #533399 where was already some discussion about the correct labeling. *** This bug has been marked as a duplicate of bug 533399 ***
*** Bug 558000 has been marked as a duplicate of this bug. ***