From: Jan Kiszka <jan.kiszka@siemens.com>
To: cip-dev@lists.cip-project.org
Cc: Sai <Sai.Sathujoda@toshiba-tsip.com>,
dinesh.kumar@toshiba-tsip.com, kazuhiro3.hayashi@toshiba.co.jp,
quirin.gylstorff@siemens.com,
Felix Moessbauer <felix.moessbauer@siemens.com>
Subject: [isar-cip-core][PATCH 0/5] Enable feature combinations of test and security extensions
Date: Thu, 2 Mar 2023 21:30:49 +0100 [thread overview]
Message-ID: <cover.1677789054.git.jan.kiszka@siemens.com> (raw)
This allows to build SWupdate/secure boot images with test extensions as
well as security extensions.
Jan
Jan Kiszka (5):
swupdate: Avoid open-coding IMAGE_FULLNAME
initramfs-*-hook: Avoid open-coding IMAGE_FULLNAME
start-qemu: Add support for booting test-extended images
cip-core-image-security: Add support for SWUpdate
security-customizations: Fix password hint
classes/swupdate.bbclass | 2 +-
kas/opt/security.yml | 3 +++
recipes-core/images/cip-core-image-security.bb | 3 +++
recipes-core/security-customizations/files/postinst | 2 +-
.../initramfs-abrootfs-hook/initramfs-abrootfs-hook_0.1.bb | 6 +++++-
.../initramfs-verity-hook/initramfs-verity-hook_0.1.bb | 6 +++++-
start-qemu.sh | 6 +++++-
7 files changed, 23 insertions(+), 5 deletions(-)
--
2.35.3
next reply other threads:[~2023-03-02 20:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-02 20:30 Jan Kiszka [this message]
2023-03-02 20:30 ` [isar-cip-core][PATCH 1/5] swupdate: Avoid open-coding IMAGE_FULLNAME Jan Kiszka
2023-03-02 20:30 ` [isar-cip-core][PATCH 2/5] initramfs-*-hook: " Jan Kiszka
2023-03-02 20:30 ` [isar-cip-core][PATCH 3/5] start-qemu: Add support for booting test-extended images Jan Kiszka
2023-03-02 20:30 ` [isar-cip-core][PATCH 4/5] cip-core-image-security: Add support for SWUpdate Jan Kiszka
2023-03-02 20:30 ` [isar-cip-core][PATCH 5/5] security-customizations: Fix password hint 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.1677789054.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=Sai.Sathujoda@toshiba-tsip.com \
--cc=cip-dev@lists.cip-project.org \
--cc=dinesh.kumar@toshiba-tsip.com \
--cc=felix.moessbauer@siemens.com \
--cc=kazuhiro3.hayashi@toshiba.co.jp \
--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 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.