All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mikko Rapeli <mikko.rapeli@linaro.org>
To: Javier Tia <javier.tia@linaro.org>
Cc: meta-arm@lists.yoctoproject.org, Ross Burton <Ross.Burton@arm.com>
Subject: Re: [PATCH v1 0/7] qemuarm64-secureboot: Enable UEFI Secure Boot
Date: Fri, 19 Jul 2024 12:49:21 +0300	[thread overview]
Message-ID: <Zpo2oSWitdFBuC2L@nuoska> (raw)
In-Reply-To: <20240718203526.52214-1-javier.tia@linaro.org>

Hi,

Is there some way to test this in oeqa runtime with ssh that
the boot was really done with secure binaries?

I think this is quite brittle and test should verify that
boot was secure.

Cheers,

-Mikko


      parent reply	other threads:[~2024-07-19  9:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18 20:35 [PATCH v1 0/7] qemuarm64-secureboot: Enable UEFI Secure Boot Javier Tia
2024-07-18 20:35 ` [PATCH v1 1/7] qemuarm64-secureboot: Add poky machine UEFI settings Javier Tia
2024-07-18 20:35 ` [PATCH v1 2/7] qemuarm64-secureboot: Introduce UEFI_SB_KEYS_DIR Javier Tia
2024-08-01 14:36   ` Jon Mason
2024-07-18 20:35 ` [PATCH v1 3/7] qemuarm64-secureboot: Validate UEFI keys exist Javier Tia
2024-07-18 20:35 ` [PATCH v1 4/7] qemuarm64-secureboot: Setup UEFI and Secure Boot in u-boot Javier Tia
2024-07-19  9:33   ` Mikko Rapeli
2024-07-18 20:35 ` [PATCH v1 5/7] qemuarm64-secureboot: Setup UEFI grub and sign EFI grub binary Javier Tia
2024-07-18 20:35 ` [PATCH v1 6/7] qemuarm64-secureboot: Setup UEFI linux-yocto and sign kernel image Javier Tia
2024-07-19  9:36   ` Mikko Rapeli
2024-07-18 20:35 ` [PATCH v1 7/7] qemuarm64-secureboot: Add UEFI systemd support Javier Tia
2024-07-19  9:47   ` Mikko Rapeli
2024-07-19  9:39 ` [PATCH v1 0/7] qemuarm64-secureboot: Enable UEFI Secure Boot Mikko Rapeli
2024-07-19  9:49 ` Mikko Rapeli [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=Zpo2oSWitdFBuC2L@nuoska \
    --to=mikko.rapeli@linaro.org \
    --cc=Ross.Burton@arm.com \
    --cc=javier.tia@linaro.org \
    --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.