From: Jonas Rebmann <jre@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Cc: Ahmad Fatoum <a.fatoum@pengutronix.de>,
Jonas Rebmann <jre@pengutronix.de>
Subject: [PATCH v2 0/2] Allow multiple keyspecs in one environment variable
Date: Wed, 18 Feb 2026 13:14:24 +0100 [thread overview]
Message-ID: <20260218-keytoc-multi-env-v2-0-3ea146c95d18@pengutronix.de> (raw)
This contains the actual change to keytoc as well a migration Note.
Allowing any number of public keys to be provided via a single
environment variable eases integration in more complex setups where
multiple public keys per keyring are managed externally.
Signed-off-by: Jonas Rebmann <jre@pengutronix.de>
---
Changes in v2:
- Split up the keyspec environment variables when multiple are provided
too.
- Use strsep_unescape instead of manual split/unescape
- Remove RFC tag
- Link to v1: https://lore.barebox.org/barebox/20260206-keytoc-multi-env-v1-1-638fbf2b3634@pengutronix.de
---
Jonas Rebmann (2):
crypto: keytoc: Split env-provided full keyspec on spaces
Documentation: migration-guides: Document change in keyspec env vars
.../migration-guides/migration-master.rst | 17 ++++++
scripts/include/linux/string.h | 2 +-
scripts/include/string_util.h | 65 ++++++++++++++++++++
scripts/keytoc.c | 71 +++++++++++++++-------
4 files changed, 132 insertions(+), 23 deletions(-)
---
base-commit: 74393178faf08f8102c7c370ac310c29112e1137
change-id: 20260206-keytoc-multi-env-4a3300292e4a
Best regards,
--
Jonas Rebmann <jre@pengutronix.de>
next reply other threads:[~2026-02-18 12:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-18 12:14 Jonas Rebmann [this message]
2026-02-18 12:14 ` [PATCH v2 1/2] crypto: keytoc: Split env-provided full keyspec on spaces Jonas Rebmann
2026-02-18 12:55 ` Marco Felsch
2026-02-19 11:43 ` Jonas Rebmann
2026-02-18 12:14 ` [PATCH v2 2/2] Documentation: migration-guides: Document change in keyspec env vars Jonas Rebmann
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=20260218-keytoc-multi-env-v2-0-3ea146c95d18@pengutronix.de \
--to=jre@pengutronix.de \
--cc=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=s.hauer@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