If a policy is built that is newer than the kernel can support, the
libsepol will fail to load that policy.
Indeed, a user can manually select the policy version in the config
as-is. However, it is not a friendly solution. The best solution available
is to set a default policy version based off of the toolchain header kernel
version. While a user may have a toolchain that has older kernel headers than
the built kernel, it is still better than setting the default to the maximum
available version that SELinux can support.
The following defaults policy versions are as follows for the given toolchain
headers:
31 >= 4.13
30 >= 4.3
29 >= 3.14
28 >= 3.5
26 >= 2.6
default 25
Note: Version 27 was never released.
Signed-off-by: Adam Duskett <aduskett@gmail.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
config BR2_PACKAGE_LIBSEPOL_POLICY_VERSION
int "Policy version"
- default 30
+ default 31 if BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_13
+ default 30 if BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_3
+ default 29 if BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_14
+ default 28 if BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_5
+ default 26 if BR2_TOOLCHAIN_HEADERS_AT_LEAST_2_6
+ default 25
+ help
+ The maximum SELinux policy version your kernel supports.
+
+ Here's a handy table to help you choose:
+ kernel version SElinux policy max version
+ <= 2.6.x 25
+ > 2.6 <= 3.5 26
+ > 3.5 <= 3.14 28 (27 and 28 were added at the same time)
+ > 3.14 <= 4.3 29
+ > 4.3 <= 4.13 30
+ > 4.13 31
endif