From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: [PATCH 1/3] kernel: enable CONFIG_SECURITY_LOCKDOWN_LSM
Date: Tue, 09 Jun 2020 18:27:16 +0000 [thread overview]
Message-ID: <c89d4e31-e8ef-362b-f713-b0c929c029c9@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2089 bytes --]
Partially fixes: #12431
Cc: Arne Fitzenreiter <arne.fitzenreiter(a)ipfire.org>
Signed-off-by: Peter Müller <peter.mueller(a)ipfire.org>
---
config/kernel/kernel.config.aarch64-ipfire | 1 +
config/kernel/kernel.config.armv5tel-ipfire-multi | 1 +
config/kernel/kernel.config.i586-ipfire | 1 +
config/kernel/kernel.config.x86_64-ipfire | 1 +
4 files changed, 4 insertions(+)
diff --git a/config/kernel/kernel.config.aarch64-ipfire b/config/kernel/kernel.config.aarch64-ipfire
index e0f2f6df8..5d51730f8 100644
--- a/config/kernel/kernel.config.aarch64-ipfire
+++ b/config/kernel/kernel.config.aarch64-ipfire
@@ -6563,6 +6563,7 @@ CONFIG_ASYNC_XOR=m
CONFIG_ASYNC_PQ=m
CONFIG_ASYNC_RAID6_RECOV=m
CONFIG_CRYPTO=y
+CONFIG_SECURITY_LOCKDOWN_LSM=y
#
# Crypto core or helper
diff --git a/config/kernel/kernel.config.armv5tel-ipfire-multi b/config/kernel/kernel.config.armv5tel-ipfire-multi
index 15183300f..f5627ba31 100644
--- a/config/kernel/kernel.config.armv5tel-ipfire-multi
+++ b/config/kernel/kernel.config.armv5tel-ipfire-multi
@@ -7045,6 +7045,7 @@ CONFIG_ASYNC_XOR=m
CONFIG_ASYNC_PQ=m
CONFIG_ASYNC_RAID6_RECOV=m
CONFIG_CRYPTO=y
+CONFIG_SECURITY_LOCKDOWN_LSM=y
#
# Crypto core or helper
diff --git a/config/kernel/kernel.config.i586-ipfire b/config/kernel/kernel.config.i586-ipfire
index 578931497..57b205ef3 100644
--- a/config/kernel/kernel.config.i586-ipfire
+++ b/config/kernel/kernel.config.i586-ipfire
@@ -6709,6 +6709,7 @@ CONFIG_ASYNC_XOR=m
CONFIG_ASYNC_PQ=m
CONFIG_ASYNC_RAID6_RECOV=m
CONFIG_CRYPTO=y
+CONFIG_SECURITY_LOCKDOWN_LSM=y
#
# Crypto core or helper
diff --git a/config/kernel/kernel.config.x86_64-ipfire b/config/kernel/kernel.config.x86_64-ipfire
index 6a5fbbfe9..840995bfe 100644
--- a/config/kernel/kernel.config.x86_64-ipfire
+++ b/config/kernel/kernel.config.x86_64-ipfire
@@ -6575,6 +6575,7 @@ CONFIG_ASYNC_XOR=m
CONFIG_ASYNC_PQ=m
CONFIG_ASYNC_RAID6_RECOV=m
CONFIG_CRYPTO=y
+CONFIG_SECURITY_LOCKDOWN_LSM=y
#
# Crypto core or helper
--
2.26.2
next reply other threads:[~2020-06-09 18:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 18:27 Peter Müller [this message]
2020-06-09 18:27 ` [PATCH 2/3] kernel: enable CONFIG_SECURITY_LOCKDOWN_LSM_EARLY Peter Müller
2020-06-09 18:28 ` [PATCH 3/3] kernel: enable CONFIG_LOCK_DOWN_KERNEL_FORCE_CONFIDENTIALITY Peter Müller
2020-06-10 14:55 ` [PATCH 1/3] kernel: enable CONFIG_SECURITY_LOCKDOWN_LSM Arne Fitzenreiter
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=c89d4e31-e8ef-362b-f713-b0c929c029c9@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.org \
/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