From: Enrico Jorns <ejo@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: ejo@pengutronix.de, jlu@pengutronix.de
Subject: [ptxdist] [PATCH 4/5] image-rauc: add support for crypt bundles
Date: Wed, 15 Jun 2022 16:22:16 +0200 [thread overview]
Message-ID: <20220615142217.990960-5-ejo@pengutronix.de> (raw)
In-Reply-To: <20220615142217.990960-1-ejo@pengutronix.de>
Signed-off-by: Enrico Jorns <ejo@pengutronix.de>
---
platforms/image-rauc.in | 8 ++++++++
rules/image-rauc.make | 12 +++++++++++-
2 files changed, 19 insertions(+), 1 deletion(-)
diff --git a/platforms/image-rauc.in b/platforms/image-rauc.in
index 3835e0718..7772fd95b 100644
--- a/platforms/image-rauc.in
+++ b/platforms/image-rauc.in
@@ -39,6 +39,14 @@ config IMAGE_RAUC_BUNDLE_FORMAT_VERITY
help
The improved 'verity' bundle format
+config IMAGE_RAUC_BUNDLE_FORMAT_CRYPT
+ bool "crypt"
+ help
+ The 'crypt' bundle format for fully encryptable bundles
+
+ Note that you must run 'rauc encrypt' on a crypt bundle to generate a
+ fully encrypted bundle.
+
endchoice
config IMAGE_RAUC_INTERMEDIATE
diff --git a/rules/image-rauc.make b/rules/image-rauc.make
index f7bed6e49..23d8d83b5 100644
--- a/rules/image-rauc.make
+++ b/rules/image-rauc.make
@@ -26,10 +26,20 @@ IMAGE_RAUC_CONFIG := rauc.config
ifdef PTXCONF_IMAGE_RAUC
+ifdef PTXCONF_IMAGE_RAUC_BUNDLE_FORMAT_PLAIN
+IMAGE_RAUC_BUNDLE_FORMAT := "plain"
+endif
+ifdef PTXCONF_IMAGE_RAUC_BUNDLE_FORMAT_VERITY
+IMAGE_RAUC_BUNDLE_FORMAT := "verity"
+endif
+ifdef PTXCONF_IMAGE_RAUC_BUNDLE_FORMAT_CRYPT
+IMAGE_RAUC_BUNDLE_FORMAT := "crypt"
+endif
+
IMAGE_RAUC_ENV = \
$(CODE_SIGNING_ENV) \
RAUC_BUNDLE_COMPATIBLE="$(call remove_quotes,$(PTXCONF_RAUC_COMPATIBLE))" \
- RAUC_BUNDLE_FORMAT="$(call ptx/ifdef,PTXCONF_IMAGE_RAUC_BUNDLE_FORMAT_VERITY,verity,plain)" \
+ RAUC_BUNDLE_FORMAT=$(IMAGE_RAUC_BUNDLE_FORMAT) \
RAUC_BUNDLE_VERSION="$(call remove_quotes, $(PTXCONF_RAUC_BUNDLE_VERSION))" \
RAUC_BUNDLE_BUILD=$(call ptx/sh, date +%FT%T%z) \
RAUC_BUNDLE_DESCRIPTION=$(PTXCONF_IMAGE_RAUC_DESCRIPTION) \
--
2.30.2
next prev parent reply other threads:[~2022-06-15 14:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 14:22 [ptxdist] [PATCH 0/5] RAUC: update to v1.7 and add some new options Enrico Jorns
2022-06-15 14:22 ` [ptxdist] [PATCH 1/5] RAUC: version bump 1.5.1 -> 1.7 Enrico Jorns
2022-06-20 6:19 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-06-15 14:22 ` [ptxdist] [PATCH 2/5] RAUC: add option to enable streaming support Enrico Jorns
2022-06-17 6:28 ` Michael Olbrich
2022-06-17 9:47 ` Enrico Jörns
2022-06-17 10:27 ` Michael Olbrich
2022-06-17 10:48 ` Michael Olbrich
2022-06-17 11:47 ` Enrico Jörns
2022-06-17 12:04 ` Michael Olbrich
2022-06-17 10:57 ` Alexander Dahl
2022-06-20 6:19 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-06-15 14:22 ` [ptxdist] [PATCH 3/5] RAUC: leverage --disable-create option to shrink size for target RAUC Enrico Jorns
2022-06-15 15:48 ` Alexander Dahl
2022-06-15 21:03 ` Enrico Jörns
2022-06-16 6:16 ` Alexander Dahl
2022-06-16 13:53 ` Enrico Jörns
2022-06-20 6:19 ` [ptxdist] [APPLIED] " Michael Olbrich
2022-06-15 14:22 ` Enrico Jorns [this message]
2022-06-20 6:20 ` [ptxdist] [APPLIED] image-rauc: add support for crypt bundles Michael Olbrich
2022-06-15 14:22 ` [ptxdist] [PATCH 5/5] image-rauc: default to 'verity' bundle format Enrico Jorns
2022-06-20 6:20 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20220615142217.990960-5-ejo@pengutronix.de \
--to=ejo@pengutronix.de \
--cc=jlu@pengutronix.de \
--cc=ptxdist@pengutronix.de \
/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