SELinux/Gentoo policy packages
Gentoo packages SELinux policy modules into their own, individual policy packages. This allows for a model where only those policy modules are loaded that are needed, instead of loading all possible policies.
SELinux policy modules
SELinux policy modules provide individual SELinux policy parts which can be loaded and unloaded at will, similar to Linux kernel modules.
As a module contains all SELinux rules related to one application (or a coherent set of applications), it makes sense to have these applications depend the SELinux policy module(s) they need.
The policy that Gentoo uses is provided through the hardened-refpolicy repository. This repository is kept up to date with the upstream commits (which is done manually, but does not take up that much effort) and contains the Gentoo-provided updates (as long as these updates aren't immediately pushed upstream).
The SELinux policy package ebuilds have the following structure:
# Copyright 1999-2014 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: /var/cvsroot/gentoo-x86/sec-policy/selinux-screen/selinux-screen-2.20140311-r2.ebuild,v 1.1 2014/04/19 14:12:46 swift Exp $
DESCRIPTION="SELinux policy for screen"
Most of the real work is done by the selinux-policy-2 eclass.
Two important variables are used by the eclass to handle the build process of a SELinux policy packages.
MODS variable contains one (or more) SELinux module names to build. These names represent the file name within the policy repository which reflects the policy to build. For instance,
MODS="screen" will look for the screen.if, screen.te and screen.fc files that provide all information of a single policy module.
BASEPOL variable contains the base version on which the policy is to be based. This is because SELinux policies call interfaces of other policies, and the content or format of these interfaces might change across versions (this backwards incompatibility is reduced as much as possible, but cannot be guaranteed). As policy modules are part of the entire repository, we take snapshots of the repository from time to time and give it the proper version (starting with the upstream version, followed by specific revisions). All policy modules from the same snapshot need to use the same
Two other interesting variables to use are:
SELINUX_GIT_REPOto point to a different Git repository which contains a refpolicy-like SELinux policy. This allows users or developers to use a different repository than the Gentoo one.
SELINUX_GIT_BRANCHis to use a different Git branch (the default is "master"), which allows users or developers to test changes before merging into the main branch.
Recently, support for
IUSE has been added so that policies can be optimized based on USE flags. For instance, modules that optionally have ALSA support can enable/disable this support in the policies through the