mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>
Cc: Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] ARM: k3: allow to take signing key from environment variable
Date: Thu, 6 Nov 2025 09:22:56 +0100	[thread overview]
Message-ID: <aQxa4LmSRqWBQQEK@pengutronix.de> (raw)
In-Reply-To: <edc3b34d-a2ed-41c3-b272-51c8cb98eaf5@pengutronix.de>

On Thu, Nov 06, 2025 at 09:02:07AM +0100, Ahmad Fatoum wrote:
> Hi,
> 
> On 06.11.25 08:30, Sascha Hauer wrote:
> > This adds a new Kconfig option CONFIG_ARCH_K3_SIGNING_KEY_ENV. With
> > this option enabled the content of CONFIG_ARCH_K3_SIGNING_KEY is treated
> > as the name of an environment variable from which the private key
> > file/uri is taken. This allows for better integration with build
> > systems.
> > 
> > Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
> > ---
> >  arch/arm/mach-k3/Kconfig |  8 ++++++++
> >  images/Makefile.k3       | 12 +++++++++++-
> >  2 files changed, 19 insertions(+), 1 deletion(-)
> > 
> > diff --git a/arch/arm/mach-k3/Kconfig b/arch/arm/mach-k3/Kconfig
> > index ecd77d8d9a..58f6ba827d 100644
> > --- a/arch/arm/mach-k3/Kconfig
> > +++ b/arch/arm/mach-k3/Kconfig
> > @@ -81,6 +81,14 @@ config ARCH_K3_SIGNING_KEY_CUSTOM
> >  
> >  endchoice
> >  
> > +config ARCH_K3_SIGNING_KEY_ENV
> > +	bool "Specify signing key in environment"
> > +	depends on ARCH_K3_SIGNING_KEY_CUSTOM
> > +	help
> > +	  If this option is enabled the content of CONFIG_ARCH_K3_SIGNING_KEY
> > +	  is treated as name of an environment variable rather than a filename/uri
> > +	  directly which allows for better integration with build systems.
> 
> Why an extra option instead of just interpreting any number of __ENV_something
> as environment variable ${something} as we already do for CONFIG_CRYPTO_PUBLIC_KEYS?

I tried but despaired at the quoting hell I got into. __ENV__something
right now is interpreted in scripts/keytoc.c which is easy.
FWIW with HAB_CERTS_ENV we have something similar to the way I have
chosen as well.

Sascha

-- 
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-11-06  8:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-06  7:30 Sascha Hauer
2025-11-06  8:02 ` Ahmad Fatoum
2025-11-06  8:22   ` Sascha Hauer [this message]
2025-11-07 14:43 ` 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=aQxa4LmSRqWBQQEK@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=a.fatoum@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