It sounds like this issue has more to do with how easily an "average"
end user can admin/modify selinux and it's policies through a GUI
interface. So what about extending the functionality of one of the
gui apps?
i.e.
-If setroubleshoot is not part of the base package, include it and
have it turned on by default
-Add audit2allow/audit2why functionality to setroubleshoot
-Simplify the details section of setroubleshoot to be more
meaningful to end-users
FWIW - I'm for keeping selinux enforcing by default, but could
definitely see where end-users could be running into issues.
Juan Velez
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
