Because we use existing provisioning for x86 OVMF. sbsign takes the private key and the cert to sign a binary. That cert then has to be added into the cert DB on the target in order to validate the

It depends on the purpose you want to create. My idea was to provide the complete PK,KEK,db structure as sankeoil and possibility to be added to the build. Your idea is to use the existing key end

I don't understand the purpose yet, specifically as the touched keys and the signing structure was already use for UEFI secure boot, on x86 and ARM[64]. It rather looks to me like you are committing a

From: Sven Schultschik <sven.schultschik@...> The snakeoil keys are copied to the deploy folder if machine is qemu-arm64. The RPMB qemu workaround is not persistent and for that the keys need

From: Sven Schultschik <sven.schultschik@...> The start-qemu shell script need some adjustments to switch on secure in the machine statement and adds the virtual random number generator if

From: Sven Schultschik <sven.schultschik@...> The secure boot setup with OP-TEE, u-boot and EFI works with a platform key (pk), key exchange key (kek) and signature database (db).

From: Sven Schultschik <sven.schultschik@...> provide a recipe to generate the needed binary to start a secure boot qemu with integrated optee and active RPMB replay protected memory

From: Sven Schultschik <sven.schultschik@...> Qemu itself is missing a implemented emulation of an RPBM (replay protected memory) which is part of an emmc. Therefore currently a u-boot patch,

From: Sven Schultschik <sven.schultschik@...> Optee is part of u-boot In the secureboot scenario to use optee and RPMB as secure storage. Signed-off-by: Sven Schultschik

From: Sven Schultschik <sven.schultschik@...> The recipe provides the possibility to create optee-os binaries for use inside of an qemu secureboot setup with edk2, rpmb, u-boot and

From: Sven Schultschik <sven.schultschik@...> provide a recipe to create the BL32_AP_MM.fd binary by edk2 which is needed for the qemu optee generation as dependency. Signed-off-by: Sven

From: Sven Schultschik <sven.schultschik@...> This series of patches will add recipes to build a QEMU setup which uses OP-TEE to use RPMB (Replay protected memory) of an EMMC for a secure

Just checking my agenda for today, and I might still be stuck in lunch break at the beginning of the meeting. Please start without me in that case! Jan

Hi all, Kindly be reminded to attend the weekly meeting through IRC to discuss technical topics with CIP kernel today. Our channel is the following: irc:irc.libera.chat:6667/cip The IRC meeting

Hi ! It's this week's CVE report. This week reported 2 new CVEs and 15 updated CVEs. * New CVEs CVE-2022-3903: An invalid pipe direction in the mceusb driver cause the kernel to DOS CVSS v3 score

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc ltp-timers: 7 runs, 10 regressions (v5.10.154-cip20-99-g0e320e4d37e4) Regressions Summary ------------------- platform | arch | lab

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc kselftest-lkdtm: 4 runs, 1 regressions (v5.10.154-cip20-99-g0e320e4d37e4) Regressions Summary ------------------- platform | arch | lab

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc baseline-nfs: 26 runs, 1 regressions (v5.10.154-cip20-99-g0e320e4d37e4) Regressions Summary ------------------- platform | arch | lab |

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc baseline: 95 runs, 2 regressions (v5.10.154-cip20-99-g0e320e4d37e4) Regressions Summary ------------------- platform | arch | lab |

cip-gitlab/ci/iwamatsu/linux-5.10.y-cip-rc build: 189 builds: 3 failed, 186 passed, 4 errors, 9 warnings (v5.10.154-cip20-99-g0e320e4d37e4) Full Build Summary: