From: Pavel Machek <pavel@ucw.cz>
To: David Howells <dhowells@redhat.com>
Cc: Ard Biesheuvel <ard.biesheuvel@linaro.org>,
mtk.manpages@gmail.com, mcgrof@kernel.org,
johannes@sipsolutions.net, linux-man@vger.kernel.org,
keyrings@vger.kernel.org, linux-security-module@vger.kernel.org,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Draft manpage explaining kernel lockdown
Date: Wed, 15 Nov 2017 22:12:46 +0100 [thread overview]
Message-ID: <20171115211246.GF6183@amd> (raw)
In-Reply-To: <7969.1507201224@warthog.procyon.org.uk>
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
Hi!
> Attached is a draft for a manual page (kernel_lockdown.7) that I intend to
> point at from messages emitted when the kernel prohibits something because the
> kernel is in 'lockdown' mode, typically triggered by EFI secure
> boot.
What about livepatching? It allows kernel modifications.. and it has
some interestlingly insecure /sys controls being merged just now...
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
prev parent reply other threads:[~2017-11-15 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 11:00 Draft manpage explaining kernel lockdown David Howells
2017-10-05 11:07 ` Johannes Berg
2017-10-05 13:16 ` David Howells
2017-10-05 18:29 ` Randy Dunlap
2017-10-05 12:33 ` Florian Weimer
2017-10-05 13:20 ` David Howells
2017-10-05 13:53 ` Ard Biesheuvel
2017-10-06 7:46 ` joeyli
2017-10-18 8:21 ` Michael Kerrisk (man-pages)
2017-11-15 21:12 ` Pavel Machek [this message]
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=20171115211246.GF6183@amd \
--to=pavel@ucw.cz \
--cc=ard.biesheuvel@linaro.org \
--cc=dhowells@redhat.com \
--cc=johannes@sipsolutions.net \
--cc=keyrings@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mcgrof@kernel.org \
--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