{"id":2132,"date":"2021-05-30T01:08:45","date_gmt":"2021-05-30T01:08:45","guid":{"rendered":"https:\/\/dft.wiki\/?p=2132"},"modified":"2026-04-21T13:34:08","modified_gmt":"2026-04-21T17:34:08","slug":"setting-up-selinux-on-ubuntu-20-04","status":"publish","type":"post","link":"https:\/\/dft.wiki\/?p=2132","title":{"rendered":"Setting Up SELinux on Ubuntu"},"content":{"rendered":"

SELinux is an upgrade to the file system that creates labels to enhance the policies for groups and users.<\/p>\n

Created by Red Hat and the NSA it also comes natively in CentOS and Fedora but can be installed in any other Linux and Unix distributions because it uses Kernel security modules.<\/p>\n

Install the packets:<\/p>\n

sudo apt update\r\nsudo apt install policycoreutils selinux-utils selinux-basics -y<\/pre>\n
Check the status and activate:<\/p>\n
sestatus\r\nsudo selinux-activate\r\nsudo reboot<\/pre>\n
\"\"<\/p>\n
Then it will reboot automatically one more time.<\/p>\n
By default, it will be permissive when enabled.<\/p>\n
\"\"<\/p>\n
The permissive mode will allow the applications to access the file even if it is not labeled accordingly but it will log everything.<\/p>\n
Enforcing will restrict access based on the labeling policy of SELinux.<\/p>\n
sudo selinux-config-enforcing\r\nsestatus<\/pre>\n
\"\"<\/p>\n
The following commands can get the current mode and set the current mode:<\/p>\n
getenforce\r\nsetenforce\r\nsetenforce 0<\/pre>\n
The mode can also be defined in the configuration file:<\/p>\n
sudo nano \/etc\/selinux\/config<\/pre>\n
The configuration file can be also modified by following the commands:<\/p>\n
sudo sed -i 's\/SELINUX=.*\/SELINUX=enforcing<\/strong>\/' \/etc\/selinux\/config<\/pre>\n
sudo sed -i 's\/SELINUX=.*\/SELINUX=permissive<\/strong>\/' \/etc\/selinux\/config<\/pre>\n
sudo sed -i 's\/SELINUX=.*\/SELINUX=disabled<\/strong>\/' \/etc\/selinux\/config<\/pre>\n
By listing the content of the directory the labels can be seen for each file:<\/p>\n
ls -Zd<\/pre>\n
Change the label:<\/p>\n
semanage fcontext -a -t FILE_TYPE<\/strong><\/span> \"\/web\"<\/pre>\n
For a webserver, the FILE_TYPE<\/strong> would be httpd_sys_content_t<\/strong><\/span>.<\/p>\n
Apply the changes:<\/p>\n
restorecon -Rv \/web<\/pre>\n
Checking the log messages:<\/p>\n
grep AVC \/var\/log\/messages<\/pre>\n
AVC (Access Vector Cache) can be understood as Access Violation.<\/p>\n
Another way is to look for Alerts on the same file:<\/p>\n
grep sealert \/var\/log\/messages<\/pre>\n
Then copy and execute the command relative to the alert you want more details, for example:<\/p>\n
sealert -l askjc1c63deb-2af3-9d23-a3247a234ab34<\/pre>\n
Note that files created will inheritance the labels from the parent directory. In the case of moving files, they will maintain the labels and will require to be re-labeled.<\/p>\n
Keep the system in permissive mode, check the logs, and apply all the necessary labels according to the applications running.<\/p>\n
In conclusion, SELinux requires a lot of work labeling all the file-system before enabling enforcing mode. Otherwise, it will crash many applications and possibly the system itself.<\/p>\n
\n
SE Linux is embedded in RHEL-based distributions and the installation of it on a Debian-based distribution looks simple but might create side effects and needs to be done very carefully.<\/p>\n
A native alternative for Debian-based dist that is not embedded but runs as a service is called AppArmor and may have a similar security feature. Read more about it at [Link<\/a>].<\/p>\n
Check out Seccomp too. It can sandbox the applications to prevent a vulnerability in it to protect the pode\/node\/cluster of a Kubernetes environment, for example. It uses a profile to allow\/deny permissions in order to restrict the process to the scope to the namespaces the app can see (as granular as per system call). Not too different but simple than apparmor and much simple than selinux but same concept.<\/p>\n","protected":false},"excerpt":{"rendered":"
SELinux is an upgrade to the file system that creates labels to enhance the policies […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[4],"tags":[],"class_list":["post-2132","post","type-post","status-publish","format-standard","hentry","category-linux"],"_links":{"self":[{"href":"https:\/\/dft.wiki\/index.php?rest_route=\/wp\/v2\/posts\/2132","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/dft.wiki\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/dft.wiki\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/dft.wiki\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/dft.wiki\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2132"}],"version-history":[{"count":10,"href":"https:\/\/dft.wiki\/index.php?rest_route=\/wp\/v2\/posts\/2132\/revisions"}],"predecessor-version":[{"id":5484,"href":"https:\/\/dft.wiki\/index.php?rest_route=\/wp\/v2\/posts\/2132\/revisions\/5484"}],"wp:attachment":[{"href":"https:\/\/dft.wiki\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2132"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/dft.wiki\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2132"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/dft.wiki\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2132"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}