From: Marco Felsch <m.felsch@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH v3 3/3] crypto: add examples to CRYPTO_PUBLIC_KEYS
Date: Mon, 18 Aug 2025 19:08:15 +0200 [thread overview]
Message-ID: <20250818170815.2478554-3-m.felsch@pengutronix.de> (raw)
In-Reply-To: <20250818170815.2478554-1-m.felsch@pengutronix.de>
It's pretty easy to get the documentation for the __ENV__ handling
wrong. Therefore add a few examples which are currently supported.
Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
---
Changelog:
v3:
- new patch
crypto/Kconfig | 18 ++++++++++++++++++
1 file changed, 18 insertions(+)
diff --git a/crypto/Kconfig b/crypto/Kconfig
index 14728be4aa91..97836a75ce5a 100644
--- a/crypto/Kconfig
+++ b/crypto/Kconfig
@@ -148,6 +148,24 @@ config CRYPTO_PUBLIC_KEYS
corresponding value in the environment variable VAR_NAME for both
public key paths/URIs as well as key name hints.
+ Examples specified directly:
+
+ - CONFIG_CRYPTO_PUBLIC_KEYS="pkcs11:object=foo"
+ - CONFIG_CRYPTO_PUBLIC_KEYS="myhint:pkcs11:object=foo"
+ - CONFIG_CRYPTO_PUBLIC_KEYS="myhint:pkcs11:object=foo /foobar/baz.der"
+ - CONFIG_CRYPTO_PUBLIC_KEYS="myhint:pkcs11:object=foo myotherhint:/foobar/baz.der"
+
+ Example specified indirectly by two environment variables:
+
+ - myhint="myhint"
+ - myname="pkcs11:object=foo" (.der could be used too)
+ - CONFIG_CRYPTO_PUBLIC_KEYS="__ENV__myhint:__ENV__myname"
+
+ Example specified indirectly by a single environment variable:
+
+ - mykey="myhint:pkcs11:object=foo" (.der could be used too)
+ - CONFIG_CRYPTO_PUBLIC_KEYS="__ENV__mykey"
+
config CRYPTO_KEYSTORE
bool "Keystore"
help
--
2.39.5
next prev parent reply other threads:[~2025-08-18 17:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-18 17:08 [PATCH v3 1/3] keytoc: mark keyspec user input as readonly Marco Felsch
2025-08-18 17:08 ` [PATCH v3 2/3] keytoc: add support to handle single env keyspec Marco Felsch
2025-08-18 17:08 ` Marco Felsch [this message]
2025-08-19 6:04 ` [PATCH v3 1/3] keytoc: mark keyspec user input as readonly 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=20250818170815.2478554-3-m.felsch@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=barebox@lists.infradead.org \
/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