From: Marco Felsch <m.felsch@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH] keytoc: fix env provided keyspec handling
Date: Wed, 23 Jul 2025 15:28:31 +0200 [thread overview]
Message-ID: <20250723132831.519984-1-m.felsch@pengutronix.de> (raw)
Currently the env provided keyspec is resolved during the gen_key() step
by making use of the try_resolve_env(). This is wrong because it will
set the complete <hint>:<key> string for the 'keyname' and 'path'.
To fix this the resolve step must happen during the main-loop as first step
because the main-loop is doing the 'keyname' and 'path' split already.
Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
---
scripts/keytoc.c | 13 +++++--------
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/scripts/keytoc.c b/scripts/keytoc.c
index c92465707f65..c1e8c51d7a7e 100644
--- a/scripts/keytoc.c
+++ b/scripts/keytoc.c
@@ -615,10 +615,6 @@ static int gen_key(const char *keyname, const char *path)
char *tmp, *key_name_c;
/* key name handling */
- keyname = try_resolve_env(keyname);
- if (!keyname)
- exit(1);
-
tmp = key_name_c = strdup(keyname);
while (*tmp) {
@@ -628,10 +624,6 @@ static int gen_key(const char *keyname, const char *path)
}
/* path/URI handling */
- path = try_resolve_env(path);
- if (!path)
- exit(1);
-
if (!strncmp(path, "pkcs11:", 7)) {
ret = engine_get_pub_key(path, &key);
if (ret)
@@ -709,6 +701,11 @@ int main(int argc, char *argv[])
char *keyname = NULL;
char *path, *freep = NULL;
+ /* Check if the keyspec is provided by the ENV first */
+ keyspec = try_resolve_env(keyspec);
+ if (!keyspec)
+ exit(1);
+
if (!strncmp(keyspec, "pkcs11:", 7)) {
path = keyspec;
} else {
--
2.39.5
next reply other threads:[~2025-07-23 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 13:28 Marco Felsch [this message]
2025-07-24 10:11 ` Marco Felsch
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=20250723132831.519984-1-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