public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Erik Schilling" <erik.schilling@linaro.org>
To: "Mikko Rapeli" <mikko.rapeli@linaro.org>,
	<openembedded-core@lists.openembedded.org>
Cc: "Michelle Lin" <michelle.linto91@gmail.com>
Subject: Re: [PATCH 3/3] uki.bbclass: add class for building Unified Kernel Images (UKI)
Date: Mon, 02 Sep 2024 12:36:52 +0200	[thread overview]
Message-ID: <D3VQDRXC0KHV.2IZTPOVXOPTOZ@linaro.org> (raw)
In-Reply-To: <20240902094117.31156-4-mikko.rapeli@linaro.org>

On Mon Sep 2, 2024 at 11:41 AM CEST, Mikko Rapeli wrote:
> From: Michelle Lin <michelle.linto91@gmail.com>
>
> This class calls systemd ukify tool, which will combine
> kernel/initrd/stub components to build the UKI. To sign the UKI
> (i.e. SecureBoot), the keys/cert files can be specified
> in a configuration file or UEFI binary signing can be done
> via separate steps, see qemuarm64-secureboot in meta-arm.
> UKIs are loaded by UEFI firmware on target which can improve
> security by loading only correctly signed kernel, initrd and kernel
> command line.
>
> Using systemd-measure to pre-calculate TPM PCR values and sign them is
> not supported since that requires a TPM device on the build host. Thus
> "ConditionSecurity=measured-uki" default from systemd 256 does not work
> but "ConditionSecurity=tpm2" in combination with secure boot will.
> These can be used to boot securely into systemd-boot, kernel, kernel
> command line and initrd which then securely mounts a read-only dm-verity
> /usr partition and creates a TPM encrypted read-write / rootfs.
>
> Tested via qemuarm64-secureboot in meta-arm with
> https://lists.yoctoproject.org/g/meta-arm/topic/patch_v3_02_13/108031399
> and a few more changes needed, will be posted separately.
>
> Signed-off-by: Michelle Lin <michelle.linto91@gmail.com>
> Cc: Erik Schilling <erik.schilling@linaro.org>
> Signed-off-by: Mikko Rapeli <mikko.rapeli@linaro.org>

> ---
>  meta/classes-recipe/uki.bbclass | 158 ++++++++++++++++++++++++++++++++
>  1 file changed, 158 insertions(+)
>  create mode 100644 meta/classes-recipe/uki.bbclass

Acked-by: Erik Schilling <erik.schilling@linaro.org>


      reply	other threads:[~2024-09-02 10:36 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02  9:41 [PATCH 0/3] systemd uki support Mikko Rapeli
2024-09-02  9:41 ` [PATCH 1/3] systemd-tools: add recipe Mikko Rapeli
2024-09-02  9:59   ` [OE-core] " Richard Purdie
2024-09-02 10:05     ` Mikko Rapeli
2024-09-02 10:17       ` Alexander Kanavin
2024-09-02 10:29         ` Mikko Rapeli
2024-09-02 10:36         ` Erik Schilling
2024-09-02  9:41 ` [PATCH 2/3] bitbake.conf: add getopt to HOSTTOOLS Mikko Rapeli
2024-09-02 10:09   ` [OE-core] " Peter Kjellerstedt
2024-09-02 10:15     ` Alexander Kanavin
2024-09-02 10:27       ` Mikko Rapeli
2024-09-02 10:34         ` Alexander Kanavin
     [not found]       ` <17F1667FB4E21297.30681@lists.openembedded.org>
2024-09-02 10:35         ` Mikko Rapeli
2024-09-02 10:15     ` Mikko Rapeli
2024-09-02  9:41 ` [PATCH 3/3] uki.bbclass: add class for building Unified Kernel Images (UKI) Mikko Rapeli
2024-09-02 10:36   ` Erik Schilling [this message]

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=D3VQDRXC0KHV.2IZTPOVXOPTOZ@linaro.org \
    --to=erik.schilling@linaro.org \
    --cc=michelle.linto91@gmail.com \
    --cc=mikko.rapeli@linaro.org \
    --cc=openembedded-core@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox