From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Michelle Lin <michelle.linto91@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] uki: Add support for building Unified Kernel Images
Date: Mon, 4 Sep 2023 09:23:56 +0300 [thread overview]
Message-ID: <ZPV3/NtaBqS0e+2s@nuoska> (raw)
In-Reply-To: <20230901233231.1109712-1-michelle.linto91@gmail.com>
Hi,
On Fri, Sep 01, 2023 at 11:32:31PM +0000, 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.
Thanks, I'm interesting in using this. Could you add a oeqa selftest for this
class too? Something which builds a UKI image and then does something to verify it
is what's expected, maybe full boot with e.g. qemu is too hard to do?
Cheers,
-Mikko
next prev parent reply other threads:[~2023-09-04 6:24 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 [this message]
2023-11-16 11:01 ` Erik Schilling
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=ZPV3/NtaBqS0e+2s@nuoska \
--to=mikko.rapeli@linaro.org \
--cc=michelle.linto91@gmail.com \
--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