From: Rasmus Villemoes <ravi@prevas.dk>
To: Brian Ruley <brian.ruley@gehealthcare.com>
Cc: Simon Glass <sjg@chromium.org>,
Alper Nebi Yasak <alpernebiyasak@gmail.com>,
Tom Rini <trini@konsulko.com>,
festevam@gmail.com, ian.ray@gehealthcare.com,
u-boot@lists.denx.de
Subject: Re: [PATCH v4 1/2] binman: nxp_imx8mcst: read certificates from input path
Date: Wed, 30 Oct 2024 13:40:36 +0100 [thread overview]
Message-ID: <87ikt9kbln.fsf@prevas.dk> (raw)
In-Reply-To: <20241030080753.129-1-brian.ruley@gehealthcare.com> (Brian Ruley's message of "Wed, 30 Oct 2024 10:07:51 +0200")
On Wed, Oct 30 2024, Brian Ruley <brian.ruley@gehealthcare.com> wrote:
> Right now, it is unclear where the certificates (and private keys) are
> read from if environment variables are unset, and providing complete
> paths in the device tree is not ideal. Naturally, it makes sense
> to be able to decide where binman should look for the files, regardless
> whether the keys are specified in the device tree or not.
>
> Therefore, expand the etype to look for the necessary files from the
> input path. Introduce a new variable to provide users the ability to
> specify a custom path.
>
> As a consequence of this change, the environment variables used to
> specify the keys, e.g., `IMG_KEY', will be searched *relative* to the
> input directories.
Hopefully not if those env variables contain an absolute path?
Rasmus
prev parent reply other threads:[~2024-10-30 12:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 13:01 [PATCH] WIP: binman: expand test coverage to nxpimx8mcst Brian Ruley
2024-10-09 1:55 ` Simon Glass
2024-10-10 11:38 ` Brian Ruley
2024-10-10 11:24 ` [PATCH v2 1/2] binman: nxp_imx8mcst: read certificates from input path Brian Ruley
2024-10-10 11:24 ` [PATCH v2 2/2] binman: expand test coverage to nxp_imx8mcst Brian Ruley
2024-10-14 21:06 ` Simon Glass
2024-10-21 7:37 ` Brian Ruley
2024-10-21 7:37 ` [PATCH v3 1/2] binman: nxp_imx8mcst: read certificates from input path Brian Ruley
2024-10-21 7:37 ` [PATCH v3 2/2] binman: expand test coverage to nxp_imx8mcst Brian Ruley
2024-10-29 15:45 ` Simon Glass
2024-10-29 16:05 ` Fabio Estevam
2024-10-30 8:07 ` [PATCH v4 1/2] binman: nxp_imx8mcst: read certificates from input path Brian Ruley
2024-10-30 8:07 ` [PATCH v4 2/2] binman: expand test coverage to nxp_imx8mcst Brian Ruley
2024-10-30 12:23 ` Fabio Estevam
2024-11-04 8:33 ` Brian Ruley
2024-11-20 12:40 ` Simon Glass
2024-12-03 11:44 ` Brian Ruley
2024-12-03 13:45 ` Simon Glass
2024-10-30 12:40 ` Rasmus Villemoes [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=87ikt9kbln.fsf@prevas.dk \
--to=ravi@prevas.dk \
--cc=alpernebiyasak@gmail.com \
--cc=brian.ruley@gehealthcare.com \
--cc=festevam@gmail.com \
--cc=ian.ray@gehealthcare.com \
--cc=sjg@chromium.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.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