From: Jan Kiszka <jan.kiszka@siemens.com>
To: U-Boot Mailing List <u-boot@lists.denx.de>
Cc: Simon Glass <sjg@chromium.org>,
Ivan Mikhaylov <ivan.mikhaylov@siemens.com>
Subject: [resent][PATCH 0/3] mkimage: allow to specify signing algorithm
Date: Fri, 14 Jan 2022 10:21:16 +0100 [thread overview]
Message-ID: <cover.1642152079.git.jan.kiszka@siemens.com> (raw)
[resent as requested by Simon]
Another step to decouple the FIT image specification from the actual
signing: With these changes, the signature nodes can leave out an algo
property, mkimage will initialize that as well while signing. This way,
in-tree FIT source files can be prepared for gaining signatures without
defining the key type or size upfront, forcing users to patch the code
to change that.
Patch 1 is preparatory for this, patch 2 a drive-by cleanup.
A better solution would actually be if the algorithm was derived from
the provided key. But the underlying crypto layer seems to be rather
unprepared for that.
Jan
Jan Kiszka (3):
image-fit: Make string of algo parameter constant
mkimage: Drop unused OPT_STRING constant
mkimage: Allow to specify the signature algorithm on the command line
boot/image-fit-sig.c | 2 +-
boot/image-fit.c | 8 +++----
doc/mkimage.1 | 5 +++++
include/image.h | 5 +++--
tools/fit_image.c | 3 ++-
tools/image-host.c | 50 +++++++++++++++++++++++++-------------------
tools/imagetool.h | 1 +
tools/mkimage.c | 6 ++++--
8 files changed, 49 insertions(+), 31 deletions(-)
--
2.31.1
next reply other threads:[~2022-01-14 9:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 9:21 Jan Kiszka [this message]
2022-01-14 9:21 ` [resent][PATCH 1/3] image-fit: Make string of algo parameter constant Jan Kiszka
2022-01-21 15:20 ` Simon Glass
2022-01-24 16:53 ` Tom Rini
2022-01-14 9:21 ` [resent][PATCH 2/3] mkimage: Drop unused OPT_STRING constant Jan Kiszka
2022-01-21 15:20 ` Simon Glass
2022-01-24 16:53 ` Tom Rini
2022-01-14 9:21 ` [resent][PATCH 3/3] mkimage: Allow to specify the signature algorithm on the command line Jan Kiszka
2022-01-21 15:20 ` Simon Glass
2022-01-24 16:53 ` Tom Rini
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=cover.1642152079.git.jan.kiszka@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=ivan.mikhaylov@siemens.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox