All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: m.grand@trustngo.tech
Cc: "meta-arm@lists.yoctoproject.org" <meta-arm@lists.yoctoproject.org>
Subject: Re: [meta-arm] Full secure boot with qemuarm64
Date: Tue, 15 Jul 2025 11:06:41 +0300	[thread overview]
Message-ID: <aHYMEYkgUWBKsuhm@nuoska> (raw)
In-Reply-To: <MR1P264MB1841ADD5E68964B57B0DA05BE157A@MR1P264MB1841.FRAP264.PROD.OUTLOOK.COM>

Hi,

On Tue, Jul 15, 2025 at 07:57:28AM +0000, Michael Grand via lists.yoctoproject.org wrote:
> Dear all,
> 
> I'm trying to develop a PoC of a fully secure embedded software. Because this PoC is intended for educational use, I don't want to depend on a specific hardware vendor and therefore, I'm using qemuarm64 as target.
> 
> Unfortunately, i'm struggling in having a working secure boot (TF-A + OP-TEE + U-boot + kernel) and I cannot find useful (and working) information on the internet. Do somebody has some kind of a minimal working secure boot example based on qemuarm64 ?

Check the meta-arm layer and build for example
"kas build ci/qemuarm64-secureboot:ci/uefi-secureboot.yml:ci/testimage.yml"

These build u-boot for UEFI secureboot and then load a UKI binary
signed with matching keys, which includes kernel and initrd.

The testimage part boots the thing with u-boot and checks that
boot was secure. The config files have the details.

Hope this helps,

-Mikko


  reply	other threads:[~2025-07-15  8:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-15  7:57 Full secure boot with qemuarm64 Michael Grand
2025-07-15  8:06 ` Mikko Rapeli [this message]
     [not found] ` <18525E398D470BE8.3909@lists.yoctoproject.org>
2025-07-15  8:19   ` [meta-arm] " Mikko Rapeli
2025-07-15 16:09     ` Michael Grand

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=aHYMEYkgUWBKsuhm@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=m.grand@trustngo.tech \
    --cc=meta-arm@lists.yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.