[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YvaJc7bQjz61Y1jj@zn.tnic>
Date: Fri, 12 Aug 2022 19:10:11 +0200
From: Borislav Petkov <bp@...e.de>
To: Stefan Berger <stefanb@...ux.ibm.com>
Cc: kexec@...ts.infradead.org, devicetree@...r.kernel.org,
linux-integrity@...r.kernel.org, linux-kernel@...r.kernel.org,
linuxppc-dev@...ts.ozlabs.org, nayna@...ux.ibm.com,
nasastry@...ibm.com, mpe@...erman.id.au,
Jonathan McDowell <noodles@...com>,
Mimi Zohar <zohar@...ux.ibm.com>
Subject: Re: [PATCH v7 3/6] x86/kexec: Carry forward IMA measurement log on
kexec
On Fri, Aug 12, 2022 at 12:43:02PM -0400, Stefan Berger wrote:
> From: Jonathan McDowell <noodles@...com>
>
> On kexec file load, the Integrity Measurement Architecture (IMA)
> subsystem may verify the IMA signature of the kernel and initramfs, and
> measure it. The command line parameters passed to the kernel in the
> kexec call may also be measured by IMA.
>
> A remote attestation service can verify a TPM quote based on the TPM
> event log, the IMA measurement list and the TPM PCR data. This can
> be achieved only if the IMA measurement log is carried over from the
> current kernel to the next kernel across the kexec call.
>
> PowerPC and ARM64 both achieve this using device tree with a
> "linux,ima-kexec-buffer" node. x86 platforms generally don't make use of
> device tree, so use the setup_data mechanism to pass the IMA buffer to
> the new kernel.
>
> Signed-off-by: Jonathan McDowell <noodles@...com>
> Signed-off-by: Borislav Petkov <bp@...e.de>
> Reviewed-by: Mimi Zohar <zohar@...ux.ibm.com> # IMA function definitions
> Link: https://lore.kernel.org/r/YmKyvlF3my1yWTvK@noodles-fedora-PC23Y6EG
Is there any particular reason to keep sending a patch which is already
upstream?
--
Regards/Gruss,
Boris.
SUSE Software Solutions Germany GmbH
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Martje Boudien Moerman
(HRB 36809, AG Nürnberg)
Powered by blists - more mailing lists