[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <5a217256a53f9c33aba4528ab0393b84c42b1813.camel@linux.ibm.com>
Date: Wed, 07 Apr 2021 12:10:04 -0400
From: Mimi Zohar <zohar@...ux.ibm.com>
To: Jarkko Sakkinen <jarkko@...nel.org>,
Stefan Berger <stefanb@...ux.ibm.com>
Cc: keyrings@...r.kernel.org, dhowells@...hat.com, nayna@...ux.ibm.com,
linux-integrity@...r.kernel.org,
linux-security-module@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/2] Add support for ECDSA-signed kernel modules
On Wed, 2021-04-07 at 18:53 +0300, Jarkko Sakkinen wrote:
> On Tue, Apr 06, 2021 at 02:53:38PM -0400, Stefan Berger wrote:
> > This series adds support for ECDSA-signed kernel modules.
> >
> > The first patch in this series attempts to address the issue where a
> > developer created an ECDSA key for signing modules and then falls back
> > to compiling an older version of the kernel that does not support
> > ECDSA keys. In this case this patch would delete that ECDSA key if it is
> > in certs/signing_key.pem and trigger the creation of an RSA key. However,
> > for this to work this patch would have to be applied to previous versions
> > of the kernel but would also only work for the developer if he/she used a
> > stable version of the kernel to which this patch was applied. So whether
> > this patch actually achieves the wanted effect is not always guaranteed.
>
> Just wondering why the key needs to be removed in the fallback.
The main concern is with bisecting the kernel. Either elliptic curve
support or the first patch needs to be backported. This patch will
cause the kernel module signing key to be regenerated.
Mimi
Powered by blists - more mailing lists