From: Tom Rini <trini@konsulko.com>
To: Alexander Dahl <ada@thorsis.com>
Cc: u-boot@lists.denx.de, Massimo Pegorer <massimo.pegorer@vimar.com>,
Simon Glass <sjg@chromium.org>,
Sean Anderson <sean.anderson@seco.com>
Subject: Re: [PATCH] mkimage: Allow 'auto-conf' signing of scripts
Date: Fri, 5 Jul 2024 16:39:32 -0600 [thread overview]
Message-ID: <20240705223932.GS38804@bill-the-cat> (raw)
In-Reply-To: <20240620142059.2348379-1-ada@thorsis.com>
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
On Thu, Jun 20, 2024 at 04:20:59PM +0200, Alexander Dahl wrote:
> U-Boot configured for verified boot with the "required" option set to
> "conf" also checks scripts put in FIT images for a valid signature, and
> refuses to source and run such a script if the signature for the
> configuration is bad or missing. Such a script could not be packaged
> before, because mkimage failed like this:
>
> % tools/mkimage -T script -C none -d tmp/my.scr -f auto-conf -k tmp -g dev -o sha256,rsa4096 my.uimg
> Failed to find any images for configuration 'conf-1/signature'
> tools/mkimage Can't add hashes to FIT blob: -1
> Error: Bad parameters for FIT image type
>
> This is especially unfortunate if LEGACY_IMAGE_FORMAT is disabled as
> recommended.
>
> Listing the script configuration in a "sign-images" subnode instead,
> would have added even more complexity to the already complex auto fit
> generation code.
>
> Signed-off-by: Alexander Dahl <ada@thorsis.com>
Applied to u-boot/master, thanks!
--
Tom
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]
prev parent reply other threads:[~2024-07-05 22:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-20 14:20 [PATCH] mkimage: Allow 'auto-conf' signing of scripts Alexander Dahl
2024-07-05 22:39 ` Tom Rini [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=20240705223932.GS38804@bill-the-cat \
--to=trini@konsulko.com \
--cc=ada@thorsis.com \
--cc=massimo.pegorer@vimar.com \
--cc=sean.anderson@seco.com \
--cc=sjg@chromium.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.