Description of problem: The devices /dev/twe* (for older 3ware controllers) have the wrong context. Similar to #232218, but in this case the driver is 3w_xxxx and the devices are /dev/twe*. This fixed it temporarily for me: for i in /dev/twe*; do chcon -t fixed_disk_device_t $i; done sealert reports this: Summary SELinux is preventing /usr/sbin/smartd (fsdaemon_t) "getattr" access to device /dev/twe0. Detailed Description SELinux has denied the /usr/sbin/smartd (fsdaemon_t) "getattr" access to device /dev/twe0. /dev/twe0 is mislabeled, this device has the default label of the /dev directory, which should not happen. Version-Release number of selected component (if applicable): selinux-policy-2.4.6-30.el5 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
The same fix for 232218 fixes this problem. *** This bug has been marked as a duplicate of 232218 ***
I'm not sure there is a fix for Bug #232218 yet, unless you mean the updated SELinux Reference Policy: http://oss.tresys.com/projects/refpolicy/changeset/2246 I assume you're the "Dan" mentioned in the ChangeLog. That's only a fix for Fedora 7. Will RHEL 5.1 or another future update include an updated SELinux Reference Policy?
Yes this should be fixed in the u1 policy. You can grab a prerelease at http://people.redhat.com/dwalsh/SELinux/RHEL5