"At this point in the development of SELinux, it's common for
policies to contain small bugs that cause operations to fail when
applications or programs are used in unusual ways unanticipated by
policy developers. As an SELinux administrator, one of the most
frequent SELinux policy customizations you're likely to perform is
adding permissions to coax the security engine into accepting an
operation. Let's consider an actual situation based on Fedora Core
2's SELinux implementation and see how it's resolved. The procedure
we'll follow isn't the only procedure or best procedure. Creating
new policies typically entails a generous dollop of
troubleshooting, which tends to be relatively unstructured. So
rather than see our procedure as the universal norm, you should see
it as merely an illustrative example..."
Some of the products that appear on this site are from companies from which QuinStreet receives compensation. This compensation may impact how and where products appear on this site including, for example, the order in which they appear. QuinStreet does not include all companies or all types of products available in the marketplace.