mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Marco Felsch <m.felsch@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: barebox@lists.infradead.org, Bastian Krause <bst@pengutronix.de>
Subject: Re: [PATCH v2 2/2] keytoc: fix env provided keyspec handling
Date: Tue, 5 Aug 2025 22:07:54 +0200	[thread overview]
Message-ID: <20250805200754.tpbu2pypgaz6gk2g@pengutronix.de> (raw)
In-Reply-To: <aJG88XTuJpuYX12B@pengutronix.de>

On 25-08-05, Sascha Hauer wrote:
> +Cc Basti
> 
> On Thu, Jul 24, 2025 at 03:50:56PM +0200, Marco Felsch wrote:
> > 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> keyspec 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 617317d6607e..105fa4b5413d 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);
> > -
> 
> This was introduced by Basti in 685cc602e0ad ("keytoc: allow __ENV__
> lookup for keyname hint") to support:
> 
> CONFIG_CRYPTO_PUBLIC_KEYS="__ENV__FIT_KEY_NAME_HINT:__ENV__FIT_KEY"

Right, albeit I don't see why there should be two separate environment
variables for specifying one keyspec entry.

> I believe this patch breaks this usecase.

Of course :-/ but at the moment the simple use-case:

__ENV__FITKEY -> FITKEY="hint:<key>"

is broken. IMHO having two separate ENV variables is rather counter
intuitive. I also found myself in the following situation:

__ENV__FITKEYS -> FITKEYS="hint:<key> hint-2:<key-2> <key-3>"

This is not supported as well. So we should really define and document
the ENV behavior.

Regards,
  Marco


> 
> Sascha
> 
> >  	if (!strncmp(path, "pkcs11:", 7)) {
> >  		ret = engine_get_pub_key(path, &key);
> >  		if (ret)
> > @@ -737,6 +729,11 @@ int main(int argc, char *argv[])
> >  		char *keyname = NULL;
> >  		char *path = 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 = strdup(keyspec);
> >  		else
> > -- 
> > 2.39.5
> > 
> > 
> > 
> 
> -- 
> 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 |
> 



  reply	other threads:[~2025-08-05 20:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-24 13:50 [PATCH v2 1/2] keytoc: make keyspec a const char pointer Marco Felsch
2025-07-24 13:50 ` [PATCH v2 2/2] keytoc: fix env provided keyspec handling Marco Felsch
2025-08-05  8:12   ` Sascha Hauer
2025-08-05 20:07     ` Marco Felsch [this message]
2025-08-06  6:16       ` Sascha Hauer
2025-08-06  7:54         ` 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=20250805200754.tpbu2pypgaz6gk2g@pengutronix.de \
    --to=m.felsch@pengutronix.de \
    --cc=barebox@lists.infradead.org \
    --cc=bst@pengutronix.de \
    --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