All of lore.kernel.org
 help / color / mirror / Atom feed
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 4/5] cip-core-image-security: Add support for SWUpdate
Date: Thu,  2 Mar 2023 21:30:53 +0100	[thread overview]
Message-ID: <eb47ff287a4397729795bb830768825728a7eade.1677789054.git.jan.kiszka@siemens.com> (raw)
In-Reply-To: <cover.1677789054.git.jan.kiszka@siemens.com>

From: Jan Kiszka <jan.kiszka@siemens.com>

This allows to enable both SWUpdate and the security-extended image at
the same time.

Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
---
 kas/opt/security.yml                           | 3 +++
 recipes-core/images/cip-core-image-security.bb | 3 +++
 2 files changed, 6 insertions(+)

diff --git a/kas/opt/security.yml b/kas/opt/security.yml
index c385a627..4d119056 100644
--- a/kas/opt/security.yml
+++ b/kas/opt/security.yml
@@ -18,3 +18,6 @@ local_conf_header:
     USERS += "root"
     USER_root[password] = "Cipsecurity@123"
     USER_root[flags] = "clear-text-password"
+  adjust-swupdate: |
+    ABROOTFS_IMAGE_RECIPE = "cip-core-image-security"
+    VERITY_IMAGE_RECIPE = "cip-core-image-security"
diff --git a/recipes-core/images/cip-core-image-security.bb b/recipes-core/images/cip-core-image-security.bb
index bfd91bd3..563de897 100644
--- a/recipes-core/images/cip-core-image-security.bb
+++ b/recipes-core/images/cip-core-image-security.bb
@@ -43,3 +43,6 @@ IMAGE_PREINSTALL += " \
 # Package names based on the distro version
 IMAGE_PREINSTALL:append:buster = " libtss2-esys0"
 IMAGE_PREINSTALL:append:bullseye = " libtss2-esys-3.0.2-0"
+
+CIP_IMAGE_OPTIONS ?= ""
+require ${CIP_IMAGE_OPTIONS}
-- 
2.35.3



  parent 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 [isar-cip-core][PATCH 0/5] Enable feature combinations of test and security extensions Jan Kiszka
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 ` Jan Kiszka [this message]
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=eb47ff287a4397729795bb830768825728a7eade.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.