From: aduskett at gmail.com <aduskett@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] linux/linux.mk: add automatic selinux config selection
Date: Thu, 12 Mar 2020 11:09:08 -0700 [thread overview]
Message-ID: <20200312180909.2948885-1-aduskett@gmail.com> (raw)
From: Adam Duskett <Aduskett@gmail.com>
Enabling SELinux support in the kernel requires several options, many of which
are in different areas. These options are as follows:
- CONFIG_AUDIT
- CONFIG_DEFAULT_SECURITY_SELINUX
- CONFIG_INET
- CONFIG_NET
- CONFIG_SECURITY
- CONFIG_SECURITY_NETWORK
- CONFIG_SECURITY_SELINUX
As such, if a user selects the libselinux package, it is much easier to select
these packages for them, much like we already do with other packages
such as systemd or iptables.
Signed-off-by: Adam Duskett <Aduskett@gmail.com>
---
linux/linux.mk | 8 ++++++++
1 file changed, 8 insertions(+)
diff --git a/linux/linux.mk b/linux/linux.mk
index 4b60f33ff3..f8c34c3dca 100644
--- a/linux/linux.mk
+++ b/linux/linux.mk
@@ -406,6 +406,14 @@ define LINUX_KCONFIG_FIXUP_CMDS
$(call KCONFIG_ENABLE_OPT,CONFIG_FB,$(@D)/.config)
$(call KCONFIG_ENABLE_OPT,CONFIG_LOGO,$(@D)/.config)
$(call KCONFIG_ENABLE_OPT,CONFIG_LOGO_LINUX_CLUT224,$(@D)/.config))
+ $(if $(BR2_PACKAGE_LIBSELINUX),
+ $(call KCONFIG_ENABLE_OPT,CONFIG_AUDIT,$(@D)/.config)
+ $(call KCONFIG_ENABLE_OPT,CONFIG_DEFAULT_SECURITY_SELINUX,$(@D)/.config)
+ $(call KCONFIG_ENABLE_OPT,CONFIG_INET,$(@D)/.config)
+ $(call KCONFIG_ENABLE_OPT,CONFIG_NET,$(@D)/.config)
+ $(call KCONFIG_ENABLE_OPT,CONFIG_SECURITY,$(@D)/.config)
+ $(call KCONFIG_ENABLE_OPT,CONFIG_SECURITY_NETWORK,$(@D)/.config)
+ $(call KCONFIG_ENABLE_OPT,CONFIG_SECURITY_SELINUX,$(@D)/.config))
endef
ifeq ($(BR2_LINUX_KERNEL_DTS_SUPPORT),y)
--
2.24.1
next reply other threads:[~2020-03-12 18:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-12 18:09 aduskett at gmail.com [this message]
2020-03-14 14:37 ` [Buildroot] [PATCH 1/1] linux/linux.mk: add automatic selinux config selection Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200312180909.2948885-1-aduskett@gmail.com \
--to=aduskett@gmail.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox