Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Erik Schilling" <erik.schilling@linaro.org>
To: "Michelle Lin" <michelle.linto91@gmail.com>,
	<openembedded-core@lists.openembedded.org>
Cc: "Mikko Rapeli" <mikko.rapeli@linaro.org>
Subject: Re: [OE-core] [PATCH] uki: Add support for building Unified Kernel Images
Date: Thu, 16 Nov 2023 12:01:13 +0100	[thread overview]
Message-ID: <CX06MBGV7SW1.U1FP0I3KC0RG@ablu-work> (raw)
In-Reply-To: <20230901233231.1109712-1-michelle.linto91@gmail.com>

On Sat Sep 2, 2023 at 1:32 AM CEST, Michelle Lin wrote:
> Currently, there is not a class to support the building of unified kernel
> images. Adding a uki.bbclass to support the creation of UKIs. This class calls
> the systemd Ukify tool, which will combine the kernel/initrd/stub components to
> build the UKI. To sign the UKI (i.e. SecureBoot, TPM PCR signing), the keys/cert
> files are to be specified in a separate configuration file, and the path to the
> file is passed to the Ukify tool. UKIs are supported by UEFI and can improve
> security through predicted TPM PCR states, and reduce the build burden due to
> its single PE binary format.
>
> Signed-off-by: Michelle Lin <michelle.linto91@gmail.com>
> ---
>  meta/classes/uki.bbclass                 | 140 +++++++++++++++++++++++
>  meta/recipes-core/systemd/systemd_254.bb |  23 ++++
>  2 files changed, 163 insertions(+)
>  create mode 100644 meta/classes/uki.bbclass

Thanks a lot for submitting this!

We are very interested into this. Do you have plans to respin this?

Happy to help where possible :).

- Erik


  parent reply	other threads:[~2023-11-16 11:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-01 23:32 [PATCH] uki: Add support for building Unified Kernel Images Michelle Lin
2023-09-02  1:04 ` [OE-core] " Alejandro Enedino Hernandez Samaniego
2023-09-02  6:53 ` Richard Purdie
2023-09-06 22:29   ` Alejandro Enedino Hernandez Samaniego
2023-11-20 12:48     ` Dmitry Baryshkov
2023-11-20 13:26       ` Bruce Ashfield
2023-11-22  1:06         ` Dmitry Baryshkov
2023-11-21 14:44   ` Erik Schilling
2023-11-22  1:09     ` Dmitry Baryshkov
2023-09-04  6:23 ` Mikko Rapeli
2023-11-16 11:01 ` Erik Schilling [this message]
2023-11-28 12:32 ` Dmitry Baryshkov
2023-11-28 12:51   ` Mikko Rapeli
2023-11-28 13:08     ` Dmitry Baryshkov

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=CX06MBGV7SW1.U1FP0I3KC0RG@ablu-work \
    --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