can be installed on a Fedora system, and attempting to use this policy has frustrated many system administrators into turning off SELinux altogether. In other words, the targeted policy is often more secure simply because it's more likely to be used.
MLS
Experimental policy to support multilevel security ( MLS). This is important for some government certifications and is not widely used outside of government. (The future MCS framework appearing in the targeted policy will use specific features of MLS for a type of discretionary access control).
In the default targeted policy, the
SELinux policies are difficult and time-consuming to write, and even more difficult to write well. Nonetheless, they have to be customized to suit the particular needs of each site. The SELinux booleans provide a compromise between complexity and flexibility, by enabling policy options to be configured without editing, compiling, and retesting the policy code.
The SELinux technology was originally developed by the U.S. National Security Agency (NSA), with several partner organizations. The kernel components of SELinux have been incorporated into the main Linux kernel releases. The Fedora project utilizes those kernel components along with customized policy and some user tools (such as versions of
8.2.3. What About...
8.2.3.1. ...using the strict or MLS policies?
These alternate policies are provided as RPM packages and are installed using
# yum install
Switch between the installed policies using the graphical configuration tool ( system-config-securitylevel from the command line, or System>Administration>'Security Level and Firewall' from the menu). When more than one policy is installed, a drop-down menu for Policy Type appears on the SELinux tab, as shown in Figure 8-8. When you change the policy, the warning dialog shown at bottom left of Figure 8-8 will appear, informing you that the policy change will cause the filesystem to be relabeled. Click Yes to approve the relabeling, and then click OK in the Security Level Configuration window. Reboot to activate the new policy.
Figure 8-8. Selecting policy using the Security Level Configuration tool
To change the policy from the command prompt, edit
# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - SELinux is fully disabled.
SELINUX=enforcing
# SELINUXTYPE= type of policy in use. Possible values are:
# targeted - Only targeted network daemons are protected.
# strict - Full SELinux protection.
SELINUXTYPE=mls
# SETLOCALDEFS= Check local definition changes
SETLOCALDEFS=0
Then create the empty file
# touch /.autorelabel
Reboot to activate the change.
Fedora development is focused on the targeted policy. Changing the policy may lead to a number of unexpected system problems!
8.2.3.2. ...booting with SELinux disabled?
If you have SELinux enabled, but your system cannot boot successfully due to an SELinux problem, you may need to temporarily disable it while you investigate.
To boot with SELinux disabled, append selinux=0 to the boot options.
8.2.4. Where Can I Learn More?
? The manpages for
? The manpage for
? The Fedora Wiki SELinux page: http://fedoraproject.org/wiki/SELinux
? The setroubleshoot Wiki page: http://fedoraproject.org/wiki/SELinux/setroubleshoot
? The NSA SELinux web site: http://www.nsa.gov/selinux/index.cfm
? The SELinux project on Sourceforge: http://selinux.sourceforge.net/
? The SELinux symposium web site: http://www.selinux-symposium.org/
? The NSA SELinux FAQ: http://www.nsa.gov/selinux/info/faq.cfm
? The Fedora SELinux FAQ: http://fedora.redhat.com/docs/selinux-faq/
? The Unofficial SELinux FAQ: http://www.crypt.gen.nz/selinux/faq.html
? The home page of Tresys, a company that has done extensive work on SELinux policy development: