After the update yesterday (11/2) of the selinux policy, selinux
exceptions are no longer reported by the desktop setroubleshoot browser.
Here's what I have in /var/log/messages:
Nov 2 10:07:21 duros yum: Updated: selinux-policy - 2.6.4-49.fc7.noarch
Nov 2 10:07:27 duros setroubleshoot: SELinux is preventing
/usr/sbin/semodule (semanage_t) "write" to pipe:[17690] (rpm_t).
For complete SELinux messages. run sealert -l
0df86965-8eea-4823-9bbe-6cdbb37d1477
Nov 2 10:07:31 duros setroubleshoot: SELinux is preventing
/usr/sbin/semodule (semanage_t) "write" to pipe:[17690] (rpm_t).
For complete SELinux messages. run sealert -l
0df86965-8eea-4823-9bbe-6cdbb37d1477
Nov 2 10:07:46 duros dbus: Can't send to audit system: USER_AVC avc:
received policyload notice (seqno=2) : exe="/bin/dbus-daemon"
(sauid=602, hostname=?, addr=?, terminal=?)
Nov 2 10:07:49 duros setroubleshoot: SELinux is preventing
/sbin/restorecon (restorecon_t) "write" to pipe:[17690] (rpm_t).
For complete SELinux messages. run sealert -l
6f51fc40-97b4-4762-804b-a03cb9fb70a1
Nov 2 10:12:56 duros yum: Updated: selinux-policy-targeted -
2.6.4-49.fc7.noarch
Nov 2 10:12:57 duros setroubleshoot: SELinux is preventing
/sbin/restorecon (restorecon_t) "write" to pipe:[17690] (rpm_t).
For complete SELinux messages. run sealert -l
6f51fc40-97b4-4762-804b-a03cb9fb70a1
Now, selinux exceptions are still logged in /var/log/messages, but no
longer trigger any desktop notification, and do not appear in the
desktop setroubleshoot browser.
Anyone else see this? Bugzilla time? Wait for f8?
<Joe
