I am on centos 6 ,I have enabled selinux and also installed setroubleshoot
yum install setroubleshoot which install all the necessary packages for sealert.
I am having some issues with sealert not giving me reports on things selinux are blocking.Example, when I access webpages, I get forbidden error, and if I put selinux in permissive state the webpage works.
SELinux on my server is constantly flooded by messages like this:
Apr 16 00:27:05 mail setroubleshoot: SELinux is preventing the rm from using potentially mislabeled files (/tmp/.font-unix). For complete SELinux messages. run sealert -l 815eab39-9258-4845-ab9a-daacf60a2b3b
Apr 16 00:27:05 mail setroubleshoot: SELinux is preventing the rm from using potentially mislabeled files (./.font-unix).
I have been using Fedora since fc17, and selinux has been giving me errors using fprintd, printer and other pre-installed applications. I have always depended upon selinux for troubleshooting purposes. I have recently upgraded to Fedora 18, and have notice no selinux alerts at all. I have checked to ensure that selinux is on and working properly, and it appears to be. With that said...
We are celebrating the SELinux 10th year anversary this year. Hard to believe it. SELinux was first introduced in Fedora Core 3 and later in Red Hat Enterprise Linux 6. For those who have never used SELinux, or would like an explanation...
We have selinux running in permissive mode on a RHEL 5.3 server. Disabling it is not an option, nor is installing a different syslog solution such as syslog-ng. I have setroubleshoot messages that keep polluting /var/log/messages.
This is a little OT, but I hope that someone here could help me privately...
The challenge is Redsleeve (EL6 for arm) was developed on armv5 and
works just fine on armv7 if you have an armv7 kernel, which I do with
the Fedora 19 remix.
I've installed F18 TC4 and it's running pretty well, with the exception of a SELinux issue that I can't resolve, probably due to the fact that I've never had any previous SELinux problems and I know nothing about it.
Anyway, it's the printer driver that is generating the error and the troubleshooting tips don't help.