From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: bugzilla-daemon@bugzilla.kernel.org,
David Howells <dhowells@redhat.com>,
Heinrich Schuchardt <xypron.glpk@gmx.de>,
Michael Kerrisk <mtk.manpages@gmail.com>
Cc: Pedro Principeza <pedro.principeza@canonical.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
dann frazier <dann.frazier@canonical.com>
Subject: Re: [Bug 213577] New: kernel_lockdown.7 seems to be incorrect about automatically enabling lockdown mode in secure boot mode
Date: Sat, 3 Jul 2021 21:01:44 +0200 [thread overview]
Message-ID: <0fd0f9af-65e8-b9fa-6487-ef28deb7e502@gmail.com> (raw)
In-Reply-To: <bug-213577-216477@https.bugzilla.kernel.org/>
Added a few CCs.
On 6/25/21 8:58 AM, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=213577
>
> Bug ID: 213577
> Summary: kernel_lockdown.7 seems to be incorrect about
> automatically enabling lockdown mode in secure boot
> mode
> Product: Documentation
> Version: unspecified
> Hardware: All
> OS: Linux
> Status: NEW
> Severity: normal
> Priority: P1
> Component: man-pages
> Assignee: documentation_man-pages@kernel-bugs.osdl.org
> Reporter: peter@typeblog.net
> Regression: No
>
> As of the time of posting, the kernel_lockdown.7 manpage [1] contains a
> description about how lockdown mode is enabled by default when using EFI secure
> boot:
>
>> On an EFI-enabled x86 or arm64 machine, lockdown will be automatically
>> enabled
> if the system boots in EFI Secure Boot mode.
>
> I have not followed lockdown development upstream recently, but it seems that
> as of today the feature described above is still a downstream patch shipped by
> some distributions like Fedora [2][3]. If this is the case, then including this
> statement in the man page would be inappropriate, since it would not apply to
> other distributions such as Arch Linux which do not include said patches.
>
> [1]:
> https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/tree/man7/kernel_lockdown.7#n31
> [2]:
> https://src.fedoraproject.org/rpms/kernel/blob/rawhide/f/Patchlist.changelog#_205
> [3]:
> https://gitlab.com/cki-project/kernel-ark/-/commit/5850c93175b9d2e1081873f4bbe08dead202cb08
>
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
parent reply other threads:[~2021-07-03 19:02 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <bug-213577-216477@https.bugzilla.kernel.org/>]
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=0fd0f9af-65e8-b9fa-6487-ef28deb7e502@gmail.com \
--to=alx.manpages@gmail.com \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=dann.frazier@canonical.com \
--cc=dhowells@redhat.com \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).