Quote:
Originally Posted by CSchwangler
1. SELinux, which is the component that produced that report, is quite extensively documented. However, assessing security risks is often up to you, since its a trade-off between what you want to do/achieve and what the designers of SELinux consider a risk. Keep in mind that SELinux is aimed at the coporate customers.
2. https://bugzilla.redhat.com/ is the link to RedHat/Fedora bug reporting tool. You need an account to be able to report bugs.
|
Boloney, nice double talk.
This is a new release and has not even hit the torrents.
There will be some selinux catchup to do.
However, if the program is not in the main Fedora install the selinux error should be reported or the user will need to do an audit2allow (if it is actually blocking something that is needed. I think is is ok as it is a bug)
There is no way for a newbie to assess a risk, fix the problem or know what the heck it about.
Only updates and reading up on the selinux tools may eventually allow a user to get by something that persists.
But selinux is a security system for any and all and works very good.
Security is needed by everyone, every where.
My system is very updated in F12 and all is clean for selinux.
selinux-policy-targeted-3.6.32-45.fc12.noarch
policycoreutils-2.0.74-17.fc12.i686
The newbies will just have to wait for updates or go to the selinux-list..
SJ