From ArchWiki
Jump to: navigation, search

Related articles

Security-Enhanced Linux (SELinux) is a Linux feature that provides a variety of security policies, including U.S. Department of Defense style mandatory access controls (MAC), through the use of Linux Security Modules (LSM) in the Linux kernel. It is not a Linux distribution, but rather a set of modifications that can be applied to Unix-like operating systems, such as Linux and BSD.

Running SELinux under a Linux distribution requires three things: An SELinux enabled kernel, SELinux Userspace tools and libraries, and SELinux Policies (mostly based on the Reference Policy). Some common Linux programs will also need to be patched/compiled with SELinux features.

Current status in Arch Linux

Current status of those elements in Arch Linux:

Name Status Available at
SELinux enabled kernel Implemented Removed since the 3.14 official Arch kernel: The main complaint was the lack of Kconfig option to disable audit by default. Available in the AUR.
SELinux Userspace tools and libraries Implemented in AUR: Work is done at
SELinux Policy Work in progress, using Reference Policy as upstream Work in progress at

Summary of changes in AUR as compared to official core packages:

Name Status and comments
linux Need a rebuild with some KConfig options enabled
coreutils Need a rebuild with --with-selinux flag to link with libselinux
cronie Need a rebuild with --with-selinux flag
dbus Need a rebuild with --enable-libaudit and --enable-selinux flags
findutils Need a rebuild with libselinux installed to enable SELinux-specific options
iproute2 Need a rebuild with --with-selinux flag
logrotate Need a rebuild with --with-selinux flag
openssh Need a rebuild with --with-selinux flag
pam Need a rebuild with --enable-selinux flag for Linux-PAM ; Need a patch for pam_unix2, which only removes a function already implemented in a recent versions of libselinux
pambase Configuration changes to add to /etc/pam.d/system-login
psmisc Need a rebuild with --with-selinux flag
shadow Need a rebuild with --with-selinux flags
sudo Need a rebuild with --with-selinux flag
systemd Need a rebuild with --enable-audit and --enable-selinux flags
util-linux Need a rebuild with --with-selinux flag

All of the other SELinux-related packages may be included without changes nor risks.

Concepts: Mandatory Access Controls

Note: This section is meant for beginners. If you know what SELinux does and how it works, feel free to skip ahead to the installation.

Before you enable SELinux, it is worth understanding what it does. Simply and succinctly, SELinux enforces Mandatory Access Controls (MACs) on Linux. In contrast to SELinux, the traditional user/group/rwx permissions are a form of Discretionary Access Control (DAC). MACs are different from DACs because security policy and its execution are completely separated.

An example would be the use of the sudo command. When DACs are enforced, sudo allows temporary privilege escalation to root, giving the process so spawned unrestricted systemwide access. However, when using MACs, if the security administrator deems the process to have access only to a certain set of files, then no matter what the kind of privilege escalation used, unless the security policy itself is changed, the process will remain constrained to simply that set of files. So if sudo is tried on a machine with SELinux running in order for a process to gain access to files its policy does not allow, it will fail.

Another set of examples are the traditional (-rwxr-xr-x) type permissions given to files. When under DAC, these are user-modifiable. However, under MAC, a security administrator can choose to freeze the permissions of a certain file by which it would become impossible for any user to change these permissions until the policy regarding that file is changed.

As you may imagine, this is particularly useful for processes which have the potential to be compromised, i.e. web servers and the like. If DACs are used, then there is a particularly good chance of havoc being wreaked by a compromised program which has access to privilege escalation.

For further information, visit wikipedia:Mandatory access control.

Installing SELinux

Package description

All SELinux related packages belong to the selinux group in the AUR.

SELinux aware system utilities

Modified coreutils package compiled with SELinux support enabled. It replaces the coreutils package
Patched ustr package needed only to build libsemanageAUR. It replaces the ustr package, which does not work with recent gcc (FS#46445).
pam-selinuxAUR and pambase-selinuxAUR
PAM package with and the underlying base package. They replace the pam and pambase packages respectively.
Modified util-linux package compiled with SELinux support enabled. It replaces the util-linux package.
An SELinux aware version of Systemd. It replaces the systemd package.
An SELinux aware version of D-Bus. It replaces the dbus package.
Patched findutils package compiled with SELinux support to make searching of files with specified security context possible. It replaces the findutils package.
iproute2 package compiled with SELinux support; for example, it adds the -Z option to ss. It replaces the iproute2 package.
Psmisc package compiled with SELinux support; for example, it adds the -Z option to killall. It replaces the psmisc package.
Shadow package compiled with SELinux support; contains a modified /etc/pam.d/login file to set correct security context for user after login. It replaces the shadow package.
Modified sudo package compiled with SELinux support which sets the security context correctly. It replaces the sudo package.
Fedora fork of Vixie cron with SELinux enabled. It replaces the cronie package.
Logrotate package compiled with SELinux support. It replaces the logrotate package.
OpenSSH package compiled with SELinux support to set security context for user sessions. It replaces the openssh package.

SELinux userspace utilities

Tools to build SELinux policy
Library for security-aware applications. Python bindings needed for semanage and setools now included.
Library for policy management. Python bindings needed for semanage and setools now included.
Library for binary policy manipulation.
SELinux core utils such as newrole, setfiles, etc.
A Python library for parsing and modifying policy source.

SELinux policy packages

Reference policy sources
Precompiled modular Reference policy with headers and documentation but without sources. Development Arch Linux Refpolicy patches included, which fixes issues related to path labeling and systemd support. These patches are also sent to Reference Policy maintainers and their inclusion in selinux-refpolicy-archAUR is mainly a way to perform updates between Refpolicy releases.

Other SELinux tools

CLI and GUI tools to manage SELinux


Preparing the Kernel

Only ext2, ext3, ext4, JFS, XFS and BtrFS filesystems are supported to use SELinux. By default, the Arch Kernel does not have the SELinux LSM enabled. If you are using Arch Linux packaged kernel (linux), there is an AUR package which adds the configuration options for SELinux, linux-selinuxAUR. Otherwise, when you are using a custom kernel, please do make sure that Xattr (Extended Attributes), CONFIG_AUDIT and CONFIG_SECURITY_SELINUX are enabled in your config. (Source: Debian Wiki)

Here is the complete list of options which need to be enabled on Linux 4.3.3 to use SELinux :

Note: If using proprietary drivers, such as NVIDIA graphics drivers, you may need to rebuild them[broken link: invalid section] for custom kernels.

There are two methods to install the requisite SELinux packages.


After all these steps, you can install a SELinux kernel (like linux-selinuxAUR) and a policy (like selinux-refpolicy-archAUR).

Using the GitHub repository

All packages are maintained at . This repository also contains a script named which builds and installs (or updates) all packages in the needed order. Here is an example of a way this script can be used in a user shell to install all packages (with downloading the GPG keys which are used to verify the source tarballs of the package):

 git clone
 cd selinux

Of course, it is possible to modify the content of before running it, for example if you already have SELinux support in your kernel.

Changing boot loader configuration

If you have installed a new kernel, make sure that you update your bootloader accordingly to boot on it. Moreover you may need to add "security=selinux selinux=1" to the kernel command line. More precisely, if the kernel configuration does not set CONFIG_DEFAULT_SECURITY_SELINUX, "security=selinux" is needed, and if it contains CONFIG_SECURITY_SELINUX_BOOTPARAM=y CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=0, "selinux=1" is needed.


Add "security=selinux selinux=1" GRUB_CMDLINE_LINUX_DEFAULT variable in /etc/default/grub Run the following command:

# grub-mkconfig -o /boot/grub/grub.cfg


Change your syslinux.cfg file by adding:

LABEL arch-selinux
         LINUX ../vmlinuz-linux-selinux
         APPEND root=/dev/sda2 ro security=selinux selinux=1
         INITRD ../initramfs-linux-selinux.img

at the end. Change "linux-selinux" to whatever kernel you are using.


Create a new loader entry, for example in /boot/loader/entries/arch-selinux.conf:

title Arch Linux SELinux
linux /vmlinuz-linux-selinux
initrd /initramfs-linux-selinux.img
options root=/dev/sda2 ro selinux=1 security=selinux

Checking PAM

A correctly set-up PAM is important to get the proper security context after login. Check for the presence of the following lines in /etc/pam.d/system-login:

# close should be the first session rule
session         required close
# open should only be followed by sessions to be executed in the user context
session         required open

Installing a policy

Warning: The reference policy as given by Tresys is not very good for Arch Linux, as almost no file is labelled correctly. However, as of writing, Archers have no other choice. If anyone has made any significant strides in addressing this problem, they are encouraged to share it, preferably on the AUR. The major problems are:
  • /lib and /usr/lib are considered different (and also /bin, /sbin, /usr/bin and /usr/sbin). This introduces some instability when applying labels to the whole system, as files in these folders may be seen with 2 (or 4) different labels.
  • systemd is not yet supported (C. PeBenito, main developer of the refpolicy, announced its willingness to work on it in its github repository in October 2014,

Policies are the mainstay of SELinux. They are what govern its behaviour. The only policy currently available in the AUR is the Reference Policy. In order to install it, you should use the source files, which may be got from the package selinux-refpolicy-srcAUR or by downloading the latest release on When using the AUR package, navigate to /etc/selinux/refpolicy/src/policy and run the following commands:

# make bare
# make conf
# make install

to install the reference policy as it is. Those who know how to write SELinux policies can tweak them to their heart's content before running the commands written above. The command takes a while to do its job and taxes one core of your system completely, so do not worry. Just sit back and let the command run for as long as it takes.

To load the reference policy run:

# make load

Then, make the file /etc/selinux/config with the following contents (Only works if you used the defaults as mentioned above. If you decided to change the name of the policy, you need to tweak the file):

# This file controls the state of SELinux on the system.
# SELINUX= can take one of these three values:
#       enforcing - SELinux security policy is enforced.
#                   Set this value once you know for sure that SELinux is configured the way you like it and that your system is ready for deployment
#       permissive - SELinux prints warnings instead of enforcing.
#                    Use this to customise your SELinux policies and booleans prior to deployment. Recommended during policy development.
#       disabled - No SELinux policy is loaded.
#                  This is not a recommended setting, for it may cause problems with file labelling
# SELINUXTYPE= takes the name of SELinux policy to
# be used. Current options are:
#       refpolicy (vanilla reference policy)
#       <custompolicy> - Substitute <custompolicy> with the name of any custom policy you choose to load

Now, you may reboot. After rebooting, run:

# restorecon -r /

to label your filesystem.

Now, make a file requiredmod.te with the contents:

module requiredmod 1.0;

require {
        type devpts_t;
        type kernel_t;
        type device_t;
        type var_run_t;
        type udev_t;
        type hugetlbfs_t;
        type udev_tbl_t;
        type tmpfs_t;
        class sock_file write;
        class unix_stream_socket { read write ioctl };
        class capability2 block_suspend;
        class dir { write add_name };
        class filesystem associate;

#============= devpts_t ==============
allow devpts_t device_t:filesystem associate;

#============= hugetlbfs_t ==============
allow hugetlbfs_t device_t:filesystem associate;

#============= kernel_t ==============
allow kernel_t self:capability2 block_suspend;

#============= tmpfs_t ==============
allow tmpfs_t device_t:filesystem associate;

#============= udev_t ==============
allow udev_t kernel_t:unix_stream_socket { read write ioctl };
allow udev_t udev_tbl_t:dir { write add_name };
allow udev_t var_run_t:sock_file write;

and run the following commands:

# checkmodule -m -o requiredmod.mod requiredmod.te
# semodule_package -o requiredmod.pp -m requiredmod.mod
# semodule -i requiredmod.pp

This is required to remove a few messages from /var/log/audit/audit.log which are a nuisance to deal with in the reference policy. This is an ugly hack and it should be made very clear that the policy so installed simply patches the reference policy in order to hide the effects of incorrect labelling.

Testing in a Vagrant virtual machine

It is possible to use Vagrant to provision a virtual Arch Linux machine with SELinux configured. This is a convenient way to test an Arch Linux system running SELinux without modifying a current system. Here are commands which can be used to achieve this:

 git clone
 cd selinux/_vagrant
 vagrant up
 vagrant ssh

Post-installation steps

You can check that SELinux is working with sestatus. You should get something like:

SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             refpolicy
Current mode:                   permissive
Mode from config file:          permissive
Policy MLS status:              disabled
Policy deny_unknown status:     allowed
Max kernel policy version:      28

To maintain correct context, you can use restorecond:

# systemctl enable restorecond

To switch to enforcing mode without rebooting, you can use:

# echo 1 > /sys/fs/selinux/enforce


If you have a swap file instead of a swap partition, issue the following commands in order to set the appropriate security context:

# semanage fcontext -a -t swapfile_t "/path/to/swapfile"
# restorecon /path/to/swapfile

Working with SELinux

SELinux defines security using a different mechanism than traditional Unix access controls. The best way to understand it is by example. For example, the SELinux security context of the apache homepage looks like the following:

$ls -lZ /var/www/html/index.html
-rw-r--r--  username username system_u:object_r:httpd_sys_content_t /var/www/html/index.html

The first three and the last columns should be familiar to any (Arch) Linux user. The fourth column is new and has the format:


To explain:

  1. User: The SELinux user identity. This can be associated to one or more roles that the SELinux user is allowed to use.
  2. Role: The SELinux role. This can be associated to one or more types the SELinux user is allowed to access.
  3. Type: When a type is associated with a process, it defines what processes (or domains) the SELinux user (the subject) can access. When a type is associated with an object, it defines what access permissions the SELinux user has to that object.
  4. Level: This optional field can also be know as a range and is only present if the policy supports MCS or MLS.

This is important in case you wish to understand how to build your own policies, for these are the basic building blocks of SELinux. However, for most purposes, there is no need to, for the reference policy is sufficiently mature. However, if you are a power user or someone with very specific needs, then it might be ideal for you to learn how to make your own SELinux policies.

This is a great series of articles for someone seeking to understand how to work with SELinux.


The place to look for SELinux errors is the systemd journal. In order to see SELinux messages related to the label system_u:system_r:policykit_t:s0 (for example), you would need to run:

# journalctl _SELINUX_CONTEXT=system_u:system_r:policykit_t:s0

Useful tools

There are some tools/commands that can greatly help with SELinux.

Restores the context of a file/directory (or recursively with -R) based on any policy rules
Change the context on a specific file

Reporting issues

Please report issues on GitHub:

See also