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 v3 17/17] Documentation: migration-2025.12.0: List changes to CONFIG_CRYPTO_PUBLIC_KEYS
Date: Thu, 06 Nov 2025 16:18:14 +0100 [thread overview]
Message-ID: <20251106-tlv-signature-v3-17-5d00ed378e75@pengutronix.de> (raw)
In-Reply-To: <20251106-tlv-signature-v3-0-5d00ed378e75@pengutronix.de>
As part of the introduction of TLV signature in public key keyrings,
there is a new interpreter for CONFIG_CRYPTO_PUBLIC_KEYS in
scripts/keytoc.c. All users should update to the new syntax and are
presented with a warning. Users with invalid characters in the legacy
syntax must change the fit-hint and will be presented with an error.
Signed-off-by: Jonas Rebmann <jre@pengutronix.de>
---
Documentation/migration-guides/migration-2025.12.0.rst | 15 +++++++++++++++
1 file changed, 15 insertions(+)
diff --git a/Documentation/migration-guides/migration-2025.12.0.rst b/Documentation/migration-guides/migration-2025.12.0.rst
index 9d368bd970..21c8d1e3f3 100644
--- a/Documentation/migration-guides/migration-2025.12.0.rst
+++ b/Documentation/migration-guides/migration-2025.12.0.rst
@@ -1,6 +1,21 @@
Release v2025.12.0
==================
+Configuration options
+---------------------
+
+* The syntax of ``CONFIG_CRYPTO_PUBLIC_KEYS`` was updated with the introduction
+ of the keyring feature. Previously, keys selected via
+ ``CONFIG_CRYPTO_PUBLIC_KEYS`` were only used for fitimage verification. Now,
+ fitimage verification uses the "fit" keyring. "fit" will be selected as the
+ default keyring for transition but a warning will be emitted when no keyring
+ is explicitly provided. Existing users should update their keyspec for
+ fitimage public keys to ``keyring=fit[,fit-hint=<fit_hint>]:<crt>``
+* The fit-hints in ``CONFIG_CRYPTO_PUBLIC_KEYS`` are now limited to identifiers
+ matching the regular expression ``[a-zA-Z][a-zA-Z0-9_-]*``. Public keys with
+ a ``fit-hint`` not conforming to this results in an error, affected key-hints
+ must be changed. Please reach out to the mailing list if this causes issues.
+
Shell
-----
--
2.51.2.535.g419c72cb8a
next prev parent reply other threads:[~2025-11-06 15:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-06 15:17 [PATCH v3 00/17] TLV-Signature and keyrings Jonas Rebmann
2025-11-06 15:17 ` [PATCH v3 01/17] lib: idr: avoid dangling else in idr_for_each_entry() Jonas Rebmann
2025-11-06 15:17 ` [PATCH v3 02/17] common: clean up TLV code Jonas Rebmann
2025-11-06 15:18 ` [PATCH v3 03/17] crypto: Add support for keyrings Jonas Rebmann
2025-11-06 15:18 ` [PATCH v3 04/17] fit: only accept keys from "fit"-keyring Jonas Rebmann
2025-11-06 15:18 ` [PATCH v3 05/17] crypto: keytoc: Rename "hint" to "fit-hint" and do not use it in identifiers Jonas Rebmann
2025-11-06 15:18 ` [PATCH v3 06/17] commands: keys: update output format to include keyring Jonas Rebmann
2025-11-06 15:18 ` [PATCH v3 07/17] commands: tlv: Error out on invalid TLVs Jonas Rebmann
2025-11-06 15:18 ` [PATCH v3 08/17] scripts: bareboxtlv-generator: Implement signature Jonas Rebmann
2025-11-06 15:18 ` [PATCH v3 09/17] scripts: bareboxtlv-generator: Increase max_size in example schema Jonas Rebmann
2025-11-06 15:18 ` [PATCH v3 10/17] common: tlv: Add TLV-Signature support Jonas Rebmann
2025-11-06 15:18 ` [PATCH v3 11/17] common: tlv: default decoder for signed TLV Jonas Rebmann
2025-11-06 15:18 ` [PATCH v3 12/17] crypto: Use "development" keys for "fit" and "tlv" keyring Jonas Rebmann
2025-11-06 15:18 ` [PATCH v3 13/17] test: py: add signature to TLV integration tests Jonas Rebmann
2025-11-06 15:18 ` [PATCH v3 14/17] ci: pytest: Add kconfig fragment for TLV signature " Jonas Rebmann
2025-11-06 15:18 ` [PATCH v3 15/17] crypto: concatenate fit development certificate with private key Jonas Rebmann
2025-11-06 15:18 ` [PATCH v3 16/17] doc/barebox-tlv: Update documentation regarding TLV-Signature Jonas Rebmann
2025-11-06 15:18 ` Jonas Rebmann [this message]
2025-11-07 8:59 ` [PATCH v3 00/17] TLV-Signature and keyrings Sascha Hauer
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=20251106-tlv-signature-v3-17-5d00ed378e75@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