From mboxrd@z Thu Jan 1 00:00:00 1970 Delivery-date: Mon, 03 Nov 2025 11:27:10 +0100 Received: from metis.whiteo.stw.pengutronix.de ([2a0a:edc0:2:b01:1d::104]) by lore.white.stw.pengutronix.de with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vFrmI-00Ep63-24 for lore@lore.pengutronix.de; Mon, 03 Nov 2025 11:27:10 +0100 Received: from bombadil.infradead.org ([2607:7c80:54:3::133]) by metis.whiteo.stw.pengutronix.de with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1vFrmI-0005AW-0Z for lore@pengutronix.de; Mon, 03 Nov 2025 11:27:10 +0100 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: Content-Type:In-Reply-To:From:References:Cc:To:Subject:MIME-Version:Date: Message-ID:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=RNdWPvRDQgYmHJSxT4ndRpPSDHAe3+vASDZJibUUK+c=; b=UZoa0swLGM3Vmb33u1exkPC/AD Ex7XsbYgVzGNGjg/8bsjQgWBTdIza+ZKcQ2hpfeE/HRfy//mOID1Kv3YjoFoGOjloZL5+ga4rGF8B wOnYCUtVTlhqNRAnEkXXJFwowzD9l+0HxgSLkFVQbmB1QeQTTGIsWjjdyzmvph0w41cNT6PNm+CLq +05NbUc+K30R1AFNLdwOh7BvbfMeofCPoAQhb7S0h016rnEykhJfTx4l6wREi0Z4RGhpsNHxaI0mr uusg/rQzgE6safxQOtGtpd+Iru98AP9cXX8zUGISzcb16MC97YcQkyRgFckt6YgXGlskKEOXj7+Q5 0+DfppFA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98.2 #2 (Red Hat Linux)) id 1vFrlm-00000009ctk-3fhq; Mon, 03 Nov 2025 10:26:38 +0000 Received: from metis.whiteo.stw.pengutronix.de ([2a0a:edc0:2:b01:1d::104]) by bombadil.infradead.org with esmtps (Exim 4.98.2 #2 (Red Hat Linux)) id 1vFrlk-00000009csk-2ICp for barebox@lists.infradead.org; Mon, 03 Nov 2025 10:26:37 +0000 Received: from ptz.office.stw.pengutronix.de ([2a0a:edc0:0:900:1d::77] helo=[127.0.0.1]) by metis.whiteo.stw.pengutronix.de with esmtp (Exim 4.92) (envelope-from ) id 1vFrli-00054r-Rc; Mon, 03 Nov 2025 11:26:34 +0100 Message-ID: <9bcaaf69-142e-446a-a30d-ba538e62097a@pengutronix.de> Date: Mon, 3 Nov 2025 11:26:34 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird To: Sascha Hauer , Jonas Rebmann Cc: BAREBOX References: <20251028-tlv-signature-v2-0-3bafce636ad7@pengutronix.de> <20251028-tlv-signature-v2-17-3bafce636ad7@pengutronix.de> Content-Language: en-US, de-DE, de-BE From: Ahmad Fatoum In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20251103_022636_590919_054C6A02 X-CRM114-Status: GOOD ( 19.79 ) X-BeenThere: barebox@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "barebox" X-SA-Exim-Connect-IP: 2607:7c80:54:3::133 X-SA-Exim-Mail-From: barebox-bounces+lore=pengutronix.de@lists.infradead.org X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on metis.whiteo.stw.pengutronix.de X-Spam-Level: X-Spam-Status: No, score=-4.1 required=4.0 tests=AWL,BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_NONE autolearn=unavailable autolearn_force=no version=3.4.2 Subject: Re: [PATCH v2 17/17] Documentation: migration-2025.11.0: List changes to CONFIG_CRYPTO_PUBLIC_KEYS X-SA-Exim-Version: 4.2.1 (built Wed, 08 May 2019 21:11:16 +0000) X-SA-Exim-Scanned: Yes (on metis.whiteo.stw.pengutronix.de) On 11/3/25 11:16 AM, Sascha Hauer wrote: > On Tue, Oct 28, 2025 at 07:03:22PM +0100, Jonas Rebmann wrote: >> 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 >> --- >> Documentation/migration-guides/migration-2025.11.0.rst | 15 +++++++++++++++ >> 1 file changed, 15 insertions(+) >> >> diff --git a/Documentation/migration-guides/migration-2025.11.0.rst b/Documentation/migration-guides/migration-2025.11.0.rst >> index a9c7abb66e..bd7fcf8126 100644 >> --- a/Documentation/migration-guides/migration-2025.11.0.rst >> +++ b/Documentation/migration-guides/migration-2025.11.0.rst > > migration-2025.12.0.rst please. Should we rethink the scheme to avoid this in future? Two suggestions come to mind: - We add migration-next.rst and migration-master.rst files, where stuff can be added and then they are renamed before release: migration-master.rst -> migration-${version}.rst migration-next.rst -> migration-master.rst -> migration-next.rst - We concatenate all migration guides into a single file and before release, a new heading is added? Cheers, Ahmad > > Sascha > >> @@ -1,6 +1,21 @@ >> Release v2025.11.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=]:`` >> +* 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. >> + >> i.MX GPIOs >> ---------- >> >> >> -- >> 2.51.2.535.g419c72cb8a >> >> > -- Pengutronix e.K. | | Steuerwalder Str. 21 | http://www.pengutronix.de/ | 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 | Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |