From: Bastian Krause <bst@pengutronix.de>
To: Ahmad Fatoum <a.fatoum@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Barebox List <barebox@lists.infradead.org>
Subject: Re: [PATCH] ARM: i.MX: HAB: Allow for semicolons in HAB environment variables
Date: Thu, 16 Jan 2025 15:34:34 +0100 [thread overview]
Message-ID: <0ca78f8e-f4bd-4790-b269-3492cc9e6eb1@pengutronix.de> (raw)
In-Reply-To: <a1344e67-323e-42f5-a985-2e56e00194ba@pengutronix.de>
On 1/16/25 2:50 PM, Ahmad Fatoum wrote:
> On 16.01.25 12:26, Bastian Krause wrote:
>> On 1/16/25 12:12 PM, Ahmad Fatoum wrote:
>>> On 16.01.25 10:38, Sascha Hauer wrote:
>>>> With CONFIG_HAB_CERTS_ENV=y, paths and PKCS#11 URIs to the HAB
>>>> certificates are taken from environment variables (allowing for better
>>>> integration with build systems). In this case these values are passed
>>>> internally via compiler macros (-D) to the imx-image host tool. PKCS#11
>>>> URIs usually contain semicolons. The semicolons didn't make it through
>>>> to the imx-image configuration file due to wrong escapes. Fix this by
>>>> expanding the environment variables using make rather than shell.
>>>>
>>>> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
>>>> ---
>>>> scripts/Makefile.lib | 2 +-
>>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>>
>>>> diff --git a/scripts/Makefile.lib b/scripts/Makefile.lib
>>>> index f195ddb7e8..7dcd8c9892 100644
>>>> --- a/scripts/Makefile.lib
>>>> +++ b/scripts/Makefile.lib
>>>> @@ -579,7 +579,7 @@ cmd_imximage_S_dcd= \
>>>> overwrite-hab-env = $(shell set -e; \
>>>> test -n "$(CONFIG_HAB_CERTS_ENV)"; \
>>>> test -n "$$$(1)"; \
>>>> - echo -D$(1)=\\\"$(shell echo $$$(1))\\\")
>>>> + echo -D$(1)=\''"${${1}}"'\')
>>>
>>> Does {} and () make a difference here?
>>
>> I don't think so. This also works:
>>
>> - echo -D$(1)=\''"${${1}}"'\')
>> + echo -D$(1)=\''"$($(1))"'\')
>
> Thanks for testing. @Sascha, can you switch to using () instead?
> Otherwise it's confusing to have $(1) on the left-hand side,
> but ${1} on the right.
Makes sense.
>
> (My personal favorite would be -D$(1)=$(call stringify,$($(1))) FWIW,
> provided that it works as intended)
Unfortunately..
- echo -D$(1)=\''"${${1}}"'\')
+ echo -D$(1)=$(call stringify,$($(1))))
..does not work if the value contains a semicolon.
Regards,
Bastian
>
> Thanks,
> Ahmad
>
>>
>> Bastian
>>
>>>
>>>> overwrite-fit-env = $(shell set -e; \
>>>> test -n "$(CONFIG_BOOTM_FITIMAGE_PUBKEY_ENV)"; \
>>>
>>>
>>
>>
>
>
--
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 |
next prev parent reply other threads:[~2025-01-16 14:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-16 9:38 Sascha Hauer
2025-01-16 10:25 ` Bastian Krause
2025-01-16 11:07 ` Sascha Hauer
2025-01-16 11:12 ` Ahmad Fatoum
2025-01-16 11:26 ` Bastian Krause
2025-01-16 13:50 ` Ahmad Fatoum
2025-01-16 14:34 ` Bastian Krause [this message]
2025-01-16 14:35 ` Ahmad Fatoum
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=0ca78f8e-f4bd-4790-b269-3492cc9e6eb1@pengutronix.de \
--to=bst@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