From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Matthew Wilcox <willy@infradead.org>,
Julian Andres Klode <julian.klode@canonical.com>
Cc: Masahiro Yamada <masahiroy@kernel.org>,
Ben Hutchings <ben@decadent.org.uk>,
linux-efi <linux-efi@vger.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@vger.kernel.org>,
efi@lists.einval.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
David Howells <dhowells@redhat.com>,
keyrings@vger.kernel.org, David Woodhouse <dwmw2@infradead.org>,
debian-kernel <debian-kernel@lists.debian.org>
Subject: Re: [PATCH v2] builddeb: Support signing kernels with the module signing key
Date: Wed, 09 Feb 2022 08:21:09 -0500 [thread overview]
Message-ID: <3d76ff7aab8cdc134aebf16af66582849bd53156.camel@HansenPartnership.com> (raw)
In-Reply-To: <YgJrypdQium7AcWV@casper.infradead.org>
On Tue, 2022-02-08 at 13:10 +0000, Matthew Wilcox wrote:
> On Tue, Feb 08, 2022 at 12:01:22PM +0100, Julian Andres Klode wrote:
> > It's worth pointing out that in Ubuntu, the generated MOK key
> > is for module signing only (extended key usage
> > 1.3.6.1.4.1.2312.16.1.2), kernels signed with it will NOT be
> > bootable.
>
> Why should these be separate keys? There's no meaningful security
> boundary between a kernel module and the ernel itself; a kernel
> modulecan, for example, write to CR3, and that's game over for
> any pretence at separation.
It's standard practice for any automated build private key to be
destroyed immediately to preserve security. Thus the modules get
signed with a per kernel ephemeral build key but the MoK key is a long
term key with a special signing infrastructure, usually burned into the
distro version of shim. The kernel signing key usually has to be long
term because you want shim to boot multiple kernels otherwise upgrading
becomes a nightmare.
James
next prev parent reply other threads:[~2022-02-09 13:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 3:11 [PATCH v2] builddeb: Support signing kernels with the module signing key Matthew Wilcox (Oracle)
2022-01-04 15:39 ` Masahiro Yamada
2022-01-04 18:13 ` Matthew Wilcox
2022-02-07 12:33 ` Masahiro Yamada
2022-02-07 13:30 ` Matthew Wilcox
2022-02-08 4:09 ` Masahiro Yamada
2022-02-08 11:01 ` Julian Andres Klode
2022-02-08 13:10 ` Matthew Wilcox
2022-02-08 16:12 ` Julian Andres Klode
2022-02-09 23:03 ` Masahiro Yamada
2022-02-09 13:21 ` James Bottomley [this message]
2022-02-09 23:04 ` Masahiro Yamada
2022-02-04 22:30 ` Matthew Wilcox
2022-02-07 13:22 ` Masahiro Yamada
2022-02-09 23:05 ` Ben Hutchings
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=3d76ff7aab8cdc134aebf16af66582849bd53156.camel@HansenPartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=ben@decadent.org.uk \
--cc=debian-kernel@lists.debian.org \
--cc=dhowells@redhat.com \
--cc=dwmw2@infradead.org \
--cc=efi@lists.einval.com \
--cc=julian.klode@canonical.com \
--cc=keyrings@vger.kernel.org \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=masahiroy@kernel.org \
--cc=willy@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.