Since I have written a few answers covering SELinux recently (2 about file labeling and another about booleans), I have been thinking if it would be useful to have some generic Q&A on common SELinux issues. I would be willing to write some, if I had a better idea on what kind of topics would be considered useful.
The default SELinux policy is used by default on RHEL/Fedora based distributions. This sometimes results in questions here about permissions problems. People asking the questions do not always realize that their problem actually is SELinux related. At least, if the problem turns out to be SELinux related the question should in my opinion include selinux tag.
Due the nature of SELinux's default policy (many applications, most daemons have their own file labeling rules, contexts and configurable booleans), a very generic answer probably isn't ever going be specific enough to mark other questions as duplicate. A specific question's answer would still need to have the specific details for the application in question (using booleans, file labeling, additional policy modules, and so on).
What I'm asking here to discuss about:
- Is having some generic Q&A regarding SELinux useful at all?
- What kind of questions and answers would be useful?
- How do I configure SELinux to allow daemons to use files in non-default locations?
- How to troubleshoot SELinux issues?
- How to install the manpage httpd_selinux? (applies to other module manpages as well)
- How to customize SELinux policy for daemon (to allow access to X)?
- Is it acceptable (or a good idea) to answer topics which are explained in multiple howtos/tutorials/FAQs elsewhere but haven't been featured in U&L SE (at least in a generic question)?