Re: [PATCH v8 1/2] certs: Trigger creation of RSA module signing key if it's... | linux-security-module

[PATCH v8 0/2] Add support for ECDSA-signed kernel modules · Stefan Berger <hidden> · 2021-06-29
[PATCH v8 2/2] certs: Add support for using elliptic curve keys for signing modules · Stefan Berger <hidden> · 2021-06-29
[PATCH v8 1/2] certs: Trigger creation of RSA module signing key if it's not an RSA key · Stefan Berger <hidden> · 2021-06-29
Re: [PATCH v8 1/2] certs: Trigger creation of RSA module signing key if it's not an RSA key · Linus Torvalds <torvalds@linux-foundation.org> · 2021-06-30
Re: [PATCH v8 1/2] certs: Trigger creation of RSA module signing key if it's not an RSA key · Jarkko Sakkinen <jarkko@kernel.org> · 2021-07-02
Re: [PATCH v8 0/2] Add support for ECDSA-signed kernel modules · Jarkko Sakkinen <jarkko@kernel.org> · 2021-07-02

Re: [PATCH v8 1/2] certs: Trigger creation of RSA module signing key if it's not an RSA key

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: 2021-06-30 19:18:02
Also in: keyrings, linux-integrity, lkml

On Tue, Jun 29, 2021 at 2:34 PM Stefan Berger
[off-list ref] wrote:

Address a kbuild issue where a developer created an ECDSA key for signing
kernel modules and then builds an older version of the kernel, when bi-
secting the kernel for example, that does not support ECDSA keys.

Thanks, these two don't confuse me any more.

                Linus

`h`	back out one level
`j`	next message in thread
`k`	previous message in thread
`l`	drill in
`Esc`	close help / fold thread tree
`?`	toggle this help