From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Cc: Quirin Gylstorff <quirin.gylstorff@siemens.com>,
Christian Storm <christian.storm@siemens.com>
Subject: [isar-cip-core][PATCH 0/5] Read-only rootfs for non-secure swupdate / cleanups / fixes
Date: Tue, 19 Apr 2022 18:06:53 +0200 [thread overview]
Message-ID: <cover.1650384418.git.jan.kiszka@siemens.com> (raw)
Unifies secure and non-secure swupdate variants further by using a
read-only rootfs in both cases. See patchs for more details.
Applies on top of "SWUpdate & EFI Boot Guard refactorings".
Jan
Jan Kiszka (5):
squashfs-img: Cosmetic cleanups
verity-img: Inherit the source image type class directly
swupdate: Make rootfs read-only also in non-secure setup
Restrict OVMF to qemu-amd64 machine
wic: Drop redundant / misleading --ondisk sda parameters
classes/secure-wic-swu-img.bbclass | 9 +-----
classes/squashfs-img.bbclass | 12 ++++----
classes/verity-img.bbclass | 10 +++++--
classes/wic-swu-img.bbclass | 23 ++++++++++++++
kas/opt/ebg-secure-boot-snakeoil.yml | 7 ++---
kas/opt/efibootguard.yml | 12 ++++----
kas/opt/swupdate.yml | 2 +-
recipes-core/images/read-only.inc | 30 -------------------
wic/ebg-signed-bootloader.inc | 2 +-
wic/ebg-sysparts.inc | 6 ++--
wic/qemu-amd64-efibootguard-secureboot.wks.in | 12 ++++----
wic/qemu-amd64-efibootguard.wks | 6 ----
wic/qemu-amd64-efibootguard.wks.in | 1 +
wic/simatic-ipc227e-efibootguard.wks | 7 -----
wic/simatic-ipc227e-efibootguard.wks.in | 1 +
wic/simatic-ipc227e.wks | 4 +--
wic/swupdate-partition.inc | 2 --
wic/x86-efibootguard.wks.in | 13 ++++++++
18 files changed, 74 insertions(+), 85 deletions(-)
delete mode 100644 recipes-core/images/read-only.inc
delete mode 100644 wic/qemu-amd64-efibootguard.wks
create mode 120000 wic/qemu-amd64-efibootguard.wks.in
delete mode 100644 wic/simatic-ipc227e-efibootguard.wks
create mode 120000 wic/simatic-ipc227e-efibootguard.wks.in
delete mode 100644 wic/swupdate-partition.inc
create mode 100644 wic/x86-efibootguard.wks.in
--
2.34.1
next reply other threads:[~2022-04-19 17:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 16:06 Jan Kiszka [this message]
2022-04-19 16:06 ` [isar-cip-core][PATCH 1/5] squashfs-img: Cosmetic cleanups Jan Kiszka
2022-04-19 16:06 ` [isar-cip-core][PATCH 2/5] verity-img: Inherit the source image type class directly Jan Kiszka
2022-04-19 16:06 ` [isar-cip-core][PATCH 3/5] swupdate: Make rootfs read-only also in non-secure setup Jan Kiszka
2022-04-19 16:06 ` [isar-cip-core][PATCH 4/5] Restrict OVMF to qemu-amd64 machine Jan Kiszka
2022-04-19 16:06 ` [isar-cip-core][PATCH 5/5] wic: Drop redundant / misleading --ondisk sda parameters 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=cover.1650384418.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=christian.storm@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=quirin.gylstorff@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