From: dann frazier <dann.frazier@canonical.com>
To: linux-man@vger.kernel.org,
Michael Kerrisk <mtk.manpages@gmail.com>,
David Howells <dhowells@redhat.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>
Cc: linux-kernel@vger.kernel.org,
Pedro Principeza <pedro.principeza@canonical.com>
Subject: [PATCH] kernel_lockdown.7: Remove description of lifting via SysRq (not upstream)
Date: Wed, 26 May 2021 11:34:55 -0600 [thread overview]
Message-ID: <20210526173455.971103-1-dann.frazier@canonical.com> (raw)
The patch that implemented lockdown lifting via SysRq ended up getting
dropped[*] before the feature was merged upstream. Having the feature
documented but unsupported has caused some confusion for our users.
[*] http://archive.lwn.net:8080/linux-kernel/CACdnJuuxAM06TcnczOA6NwxhnmQUeqqm3Ma8btukZpuCS+dOqg@mail.gmail.com/
Signed-off-by: dann frazier <dann.frazier@canonical.com>
---
man7/kernel_lockdown.7 | 6 ------
1 file changed, 6 deletions(-)
diff --git a/man7/kernel_lockdown.7 b/man7/kernel_lockdown.7
index 30863de62..29ffd55c3 100644
--- a/man7/kernel_lockdown.7
+++ b/man7/kernel_lockdown.7
@@ -33,12 +33,6 @@ where X indicates the process name and Y indicates what is restricted.
.PP
On an EFI-enabled x86 or arm64 machine, lockdown will be automatically enabled
if the system boots in EFI Secure Boot mode.
-.PP
-If the kernel is appropriately configured, lockdown may be lifted by typing
-the appropriate sequence on a directly attached physical keyboard.
-For x86 machines, this is
-.IR SysRq+x .
-.\"
.SS Coverage
When lockdown is in effect, a number of features are disabled or have their
use restricted.
--
2.31.1
next reply other threads:[~2021-05-26 17:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 17:34 dann frazier [this message]
2021-05-27 7:13 ` Alejandro Colomar (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=20210526173455.971103-1-dann.frazier@canonical.com \
--to=dann.frazier@canonical.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=pedro.principeza@canonical.com \
--cc=xypron.glpk@gmx.de \
/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
all inboxes | Powered by JetHome®