From: Heinrich Schuchardt <xypron.glpk@gmx.de>
To: Michael Kerrisk <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>,
Matthew Garrett <mjg59@google.com>,
Ard Biesheuvel <ardb@kernel.org>,
David Howells <dhowells@redhat.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Subject: [PATCH 1/1] kernel_lockdown.7: describe LSM activation
Date: Fri, 16 Oct 2020 21:03:37 +0200 [thread overview]
Message-ID: <20201016190337.5126-1-xypron.glpk@gmx.de> (raw)
Describe the activation of the Kernel Lockdown feature via Kconfig and the
command line.
Cf. Documentation/admin-guide/kernel-parameters.rst.
Signed-off-by: Heinrich Schuchardt <xypron.glpk@gmx.de>
---
man7/kernel_lockdown.7 | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/man7/kernel_lockdown.7 b/man7/kernel_lockdown.7
index 04de4d1fe..5aedd96e9 100644
--- a/man7/kernel_lockdown.7
+++ b/man7/kernel_lockdown.7
@@ -104,4 +104,17 @@ whether or not they are specified on the command line,
for both the built-in and custom policies in secure boot lockdown mode.
.SH VERSIONS
The Kernel Lockdown feature was added in Linux 5.4.
+.SH NOTES
+The Kernel Lockdown feature is enabled by CONFIG_SECURITY_LOCKDOWN_LSM.
+The
+.I lsm=lsm1,...,lsmN
+command line parameter controls the sequence of the initialization of
+Linux Security Modules.
+It must contain the string
+.I lockdown
+to enable the Kernel Lockdown feature.
+If the command line parameter is not specified,
+the initialization falls back to the value of the deprecated
+.I security=
+command line parameter and further to the value of CONFIG_LSM.
.\" commit 000d388ed3bbed745f366ce71b2bb7c2ee70f449
--
2.28.0
next reply other threads:[~2020-10-16 19:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-16 19:03 Heinrich Schuchardt [this message]
2020-10-17 10:25 ` [PATCH 1/1] kernel_lockdown.7: describe LSM activation Michael Kerrisk (man-pages)
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=20201016190337.5126-1-xypron.glpk@gmx.de \
--to=xypron.glpk@gmx.de \
--cc=ardb@kernel.org \
--cc=dhowells@redhat.com \
--cc=linux-man@vger.kernel.org \
--cc=mjg59@google.com \
--cc=mtk.manpages@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).