[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f78d11fefd13bd17748e36621acee9c2f27a77f6.camel@kernel.org>
Date: Fri, 11 Mar 2022 18:42:33 +0200
From: Jarkko Sakkinen <jarkko@...nel.org>
To: Nageswara Sastry <rnsastry@...ux.ibm.com>,
Nayna Jain <nayna@...ux.ibm.com>,
linux-integrity@...r.kernel.org, keyrings@...r.kernel.org
Cc: dhowells@...hat.com, zohar@...ux.ibm.com,
linux-security-module@...r.kernel.org,
linux-kernel@...r.kernel.org, dimitri.ledkov@...onical.com,
seth@...shee.me, Masahiro Yamada <masahiroy@...nel.org>
Subject: Re: [PATCH v11 0/4] integrity: support including firmware
".platform" keys at build time
On Fri, 2022-03-11 at 10:11 +0530, Nageswara Sastry wrote:
>
>
> On 11/03/22 3:14 am, Nayna Jain wrote:
> > Some firmware support secure boot by embedding static keys to verify the
> > Linux kernel during boot. However, these firmware do not expose an
> > interface for the kernel to load firmware keys onto the ".platform"
> > keyring, preventing the kernel from verifying the kexec kernel image
> > signature.
> >
> > This patchset exports load_certificate_list() and defines a new function
> > load_builtin_platform_cert() to load compiled in certificates onto the
> > ".platform" keyring.
> >
> > Changelog:
> > v11:
> > * Added a new patch to conditionally build extract-cert if
> > PLATFORM_KEYRING is enabled.
> >
>
> Tested the following four patches with and with out setting
> CONFIG_INTEGRITY_PLATFORM_KEYS
>
> Tested-by: Nageswara R Sastry <rnsastry@...ux.ibm.com>
OK, I added it:
git://git.kernel.org/pub/scm/linux/kernel/git/jarkko/linux-tpmdd.git
BR, Jarkko
Powered by blists - more mailing lists