From: "Su, Bao Cheng" <baocheng.su@siemens.com>
To: "Schultschik, Sven" <sven.schultschik@siemens.com>,
"cip-dev@lists.cip-project.org" <cip-dev@lists.cip-project.org>
Cc: "Kiszka, Jan" <jan.kiszka@siemens.com>
Subject: Re: [isar-cip-core][PATCH 0/8] Secureboot on QEMU with EDK2, OP-TEE and RPBM
Date: Tue, 25 Oct 2022 08:09:10 +0000 [thread overview]
Message-ID: <23b969e6df97fb95a7e5fefe68c4a01a4c4fe7c7.camel@siemens.com> (raw)
In-Reply-To: <20221024122725.383791-1-sven.schultschik@siemens.com>
On Mon, 2022-10-24 at 14:27 +0200, sven.schultschik@siemens.com wrote:
> From: Sven Schultschik <sven.schultschik@siemens.com>
>
> This series of patches will add recipes to build a QEMU setup
> which uses OP-TEE to use RPBM (Replay protected memory) of
> an EMMC for a secure storage. Which is used within Secureboot
> on ARM64. QEMU itself does not have an implementation of a
> virtual RPBM. Therefore a patch for u-boot is needed which
> adds this feature to u-boot, but breaks hardware
> compatibility within u-boot. As soon as QEMU has a native
> RPMB support included, the patch can be removed.
>
Part of this patch could also be integrated into real setup, besides
QEMU?
By the way, s/RPBM/RPMB/
> The last patch is ment for manually test and verify the
> patches, but should not be merged.
>
> Sven Schultschik (8):
> add recipe for edk2
> add recipe for optee qemu arm64
> Include optee into u-boot
> add u-boot patch for qemu to support RPMB
> add recipe for trusted firmware a qemu arm64
> add kas files for building qemu secure boot images
> enhance start-qemu.sh for arm64 secure boot
> no merge - manually instructions test secure boot
>
> README.md | 65 +
> kas/opt/u-boot-efi-ebg-op-tee-qemu.yml | 11 +
> keys/helloworld.efi | Bin 0 -> 4576 bytes
> recipes-bsp/edk2/edk2_202205.bb | 43 +
> recipes-bsp/edk2/files/rules.tmpl | 61 +
> .../op-tee/optee-os-qemu-arm64_3.17.0.bb | 54 +
> .../trusted-firmware-a-qemu-arm64_2.7.0.bb | 61 +
> ...hack.-Breaks-proper-hardware-support.patch | 1375 +++++++++++++++++
> recipes-bsp/u-boot/files/secure-boot.cfg.tmpl | 9 +-
> recipes-bsp/u-boot/u-boot-qemu-common.inc | 5 +
> start-qemu.sh | 14 +-
> 11 files changed, 1695 insertions(+), 3 deletions(-)
> create mode 100644 kas/opt/u-boot-efi-ebg-op-tee-qemu.yml
> create mode 100644 keys/helloworld.efi
> create mode 100644 recipes-bsp/edk2/edk2_202205.bb
> create mode 100755 recipes-bsp/edk2/files/rules.tmpl
> create mode 100644 recipes-bsp/op-tee/optee-os-qemu-arm64_3.17.0.bb
> create mode 100644 recipes-bsp/trusted-firmware-a/trusted-firmware-a-qemu-arm64_2.7.0.bb
> create mode 100644 recipes-bsp/u-boot/files/0002-rpmb-emulation-hack.-Breaks-proper-hardware-support.patch
>
next prev parent reply other threads:[~2022-10-25 8:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-24 12:27 [isar-cip-core][PATCH 0/8] Secureboot on QEMU with EDK2, OP-TEE and RPBM sven.schultschik
2022-10-24 12:27 ` [isar-cip-core][PATCH 1/8] add recipe for edk2 sven.schultschik
2022-10-25 8:23 ` Su, Bao Cheng
2022-10-26 14:44 ` AW: " Schultschik, Sven
2022-10-27 1:39 ` Su, Bao Cheng
2022-10-27 16:14 ` AW: " Schultschik, Sven
2022-10-27 17:08 ` Jan Kiszka
2022-10-25 8:40 ` Su, Bao Cheng
2022-10-24 12:27 ` [isar-cip-core][PATCH 2/8] add recipe for optee qemu arm64 sven.schultschik
2022-10-24 12:27 ` [isar-cip-core][PATCH 3/8] Include optee into u-boot sven.schultschik
2022-10-26 7:36 ` Su, Bao Cheng
2022-10-26 8:52 ` Jan Kiszka
2022-10-26 15:27 ` AW: " Schultschik, Sven
2022-10-26 16:00 ` Jan Kiszka
2022-11-07 16:57 ` AW: " Schultschik, Sven
2022-11-07 17:50 ` Jan Kiszka
2022-11-10 11:01 ` AW: " Schultschik, Sven
2022-11-10 13:38 ` Jan Kiszka
2022-10-24 12:27 ` [isar-cip-core][PATCH 4/8] add u-boot patch for qemu to support RPMB sven.schultschik
2022-10-24 12:27 ` [isar-cip-core][PATCH 5/8] add recipe for trusted firmware a qemu arm64 sven.schultschik
2022-10-28 5:50 ` Jan Kiszka
2022-10-28 15:46 ` AW: " Schultschik, Sven
2022-10-28 19:10 ` Jan Kiszka
2022-10-24 12:27 ` [isar-cip-core][PATCH 6/8] add kas files for building qemu secure boot images sven.schultschik
2022-10-27 17:17 ` Jan Kiszka
2022-11-07 10:43 ` AW: " Schultschik, Sven
2022-11-07 12:59 ` Jan Kiszka
2022-10-24 12:27 ` [isar-cip-core][PATCH 7/8] enhance start-qemu.sh for arm64 secure boot sven.schultschik
2022-10-24 12:27 ` [isar-cip-core][PATCH 8/8] no merge - manually instructions test " sven.schultschik
2022-10-25 8:36 ` Su, Bao Cheng
2022-10-25 15:23 ` AW: " Schultschik, Sven
2022-10-25 8:09 ` Su, Bao Cheng [this message]
2022-10-25 8:16 ` [isar-cip-core][PATCH 0/8] Secureboot on QEMU with EDK2, OP-TEE and RPBM Jan Kiszka
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=23b969e6df97fb95a7e5fefe68c4a01a4c4fe7c7.camel@siemens.com \
--to=baocheng.su@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=jan.kiszka@siemens.com \
--cc=sven.schultschik@siemens.com \
/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