NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
ac2b20074a
kumquat-buildroot/package/libsepol/Config.in

36 lines
1.0 KiB
Plaintext
Raw Normal View History

libsepol: new package [Peter: white space fixes] Signed-off-by: Clayton Shotwell <clshotwe@rockwellcollins.com> Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-09-11 23:59:21 +02:00
config BR2_PACKAGE_LIBSEPOL
bool "libsepol"
libsepol: require threads libsepol 2.7 now uses <pthread.h> Fixes: http://autobuild.buildroot.net/results/5f1c6872a395d8c6d55e2b1722730871b4daf6a3 Signed-off-by: Adam Duskett <aduskett@gmail.com> Tested-by: Matt Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-11-03 14:33:06 +01:00
depends on BR2_TOOLCHAIN_HAS_THREADS # pthread
libsepol: new package [Peter: white space fixes] Signed-off-by: Clayton Shotwell <clshotwe@rockwellcollins.com> Acked-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-09-11 23:59:21 +02:00
help
Libsepol is the binary policy manipulation library. It doesn't
depend upon or use any of the other SELinux components.
http://selinuxproject.org/page/Main_Page
libsepol: require threads libsepol 2.7 now uses <pthread.h> Fixes: http://autobuild.buildroot.net/results/5f1c6872a395d8c6d55e2b1722730871b4daf6a3 Signed-off-by: Adam Duskett <aduskett@gmail.com> Tested-by: Matt Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-11-03 14:33:06 +01:00
package/{refpolicy,libsepol}: move policy version selection from refpolicy to libsepol Currently, a user sets a policy version via the refpolicy package. Having the option here has a few disadvantages: - The Refpolicy package is not technically needed to use SELinux. - When building a modular policy, Refpolicy will ignore the version string and build the highest version possible which will cause libsemanage to possibly fail when loading the policy. Specifying a manual policy version in /etc/selinux/semanage.conf forces libsemanage to load a specific policy version, which fixes the above issue. However, because refpolicy currently defines the policy version, libsemanage does not have a way to determine the policy version, as refpolicy is not a dependency of libsemanage. To work around these limitations, move the policy version number selection to libsepol, as a system using SELinux always requires this library. Signed-off-by: Adam Duskett <aduskett@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-02-03 14:29:49 +01:00
if BR2_PACKAGE_LIBSEPOL
config BR2_PACKAGE_LIBSEPOL_POLICY_VERSION
package/libsepol: change policy version to an int The policy version has to be a number, as such, set the type to int. Due to the type change, we can't any longer do the legacy handling of re-using the refpolicy policy version. Signed-off-by: Adam Duskett <aduskett@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-02-03 14:29:50 +01:00
int "Policy version"
package/libsepol: set default policy version 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>
2020-02-03 14:29:51 +01:00
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
package/{refpolicy,libsepol}: move policy version selection from refpolicy to libsepol Currently, a user sets a policy version via the refpolicy package. Having the option here has a few disadvantages: - The Refpolicy package is not technically needed to use SELinux. - When building a modular policy, Refpolicy will ignore the version string and build the highest version possible which will cause libsemanage to possibly fail when loading the policy. Specifying a manual policy version in /etc/selinux/semanage.conf forces libsemanage to load a specific policy version, which fixes the above issue. However, because refpolicy currently defines the policy version, libsemanage does not have a way to determine the policy version, as refpolicy is not a dependency of libsemanage. To work around these limitations, move the policy version number selection to libsepol, as a system using SELinux always requires this library. Signed-off-by: Adam Duskett <aduskett@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-02-03 14:29:49 +01:00
endif
libsepol: require threads libsepol 2.7 now uses <pthread.h> Fixes: http://autobuild.buildroot.net/results/5f1c6872a395d8c6d55e2b1722730871b4daf6a3 Signed-off-by: Adam Duskett <aduskett@gmail.com> Tested-by: Matt Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-11-03 14:33:06 +01:00
comment "libsepol needs a toolchain w/ threads"
depends on !BR2_TOOLCHAIN_HAS_THREADS
Reference in New Issue Copy Permalink