mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jonas Rebmann <jre@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH RFC] crypto: keytoc: Split env-provided full keyspec on spaces
Date: Tue, 10 Feb 2026 11:36:55 +0100	[thread overview]
Message-ID: <acd62e15-7c92-49f2-9bf5-c8d1245be019@pengutronix.de> (raw)
In-Reply-To: <e7c30179-bdbe-49d0-85cf-a415701a53eb@pengutronix.de>

Hi Ahmad,

On 2026-02-10 10:35, Ahmad Fatoum wrote:
> On 2/6/26 1:28 PM, Jonas Rebmann wrote:
>> keytoc/CONFIG_CRYPTO_PUBLIC_KEYS can work with a complete keyspec
>> provided by an environment variable as opposed to providing single URIs.
>> This would be a very useful feature if it could also provide any number
>> of keys. Kconfig however provides keytoc with regular keyspecs already
>> split at spaces so without furhter measures, the env variable can only
>> be expanded into a single key.
>>
>> Work around this by, in the special case of keytoc provided with a
>> single environment variable, splitting that single argument at any space
>> character that is not escaped with a backslash in front of it.
> 
> I think that's sensible. Do we see breakage potential for existing
> users? If so, we should have a migration entry about the change in
> interpretation of space.

It does break for users of the single-env-variable format if they'd been
relying on paths containing spaces or backslashes, which they'd need to
start escaping now. But I don't suppose many, if any, users are really
affected by that.

I'll add a migration entry, suppose it can't hurt.

I'll update this patch to treat multiple variables the same way as
single variables.

Right now, given a single __ENV__var1 argument, that is split but once
given a second __ENV__var2 argument, neither are split, which is
inconsistent.

I will keep not modifying plain URIs provided by env e.g.
keyring:__ENV__uri

>>   	keycount = argc - optind;
>> +	keyspecs = argv + optind;
>> +
>> +	if (keycount == 1 && !strncmp(argv[optind], "__ENV__", 7)) {
>> +		char *singlespec = try_resolve_env(keyspecs[0]);
>> +		/* include '\0' in length */
>> +		int len = strlen(singlespec) + 1;
>> +		char *p;
>> +
>> +		for (p = singlespec; *p; p++) {
> 
> Can you copy strsep_unescaped to scripts/ and use that instead?

Oh yes that will make things easier.

Regards,
Jonas

-- 
Pengutronix e.K.                           | Jonas Rebmann               |
Steuerwalder Str. 21                       | http://www.pengutronix.de/  |
31137 Hildesheim, Germany                  | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-9    |



      reply	other threads:[~2026-02-10 10:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-06 12:28 Jonas Rebmann
2026-02-10  9:35 ` Ahmad Fatoum
2026-02-10 10:36   ` Jonas Rebmann [this message]

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=acd62e15-7c92-49f2-9bf5-c8d1245be019@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