From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: Roman Kopytin <Roman.Kopytin@kaspersky.com>,
Simon Glass <sjg@chromium.org>
Cc: Thomas Perrot <thomas.perrot@bootlin.com>,
Michael Nazzareno Trimarchi <michael@amarulasolutions.com>,
U-Boot-Denx <u-boot@lists.denx.de>,
Alex Kiernan <alex.kiernan@gmail.com>
Subject: Re: U-boot
Date: Mon, 2 Aug 2021 11:37:27 +0200 [thread overview]
Message-ID: <0e75f275-d661-7b75-6da8-91ecec53d78c@prevas.dk> (raw)
In-Reply-To: <55a1a03c621f4cdea36f12ebd2cde976@kaspersky.com>
On 02/08/2021 11.25, Roman Kopytin wrote:
> Thanks a lot!
> Yes, looks like using of the 'fdtput' is not very safety for me.
> As I understood I need to use "fdt_add_pubkey" tool with CMD (example):
> ./ fdt_add_pubkey -a rsa2048 -k <keydir> -n <keyname> -r <conf|image> my_file.dtb
>
> -r <conf|image> is the same as for mkimage? As I remember we can use -r w/o any values in mkimage.
Yes, that's very close to what our Yocto recipe currently does:
for b in ${KERNEL_PUBLIC_KEYS} ; do
fdt_add_pubkey -a 'sha1,rsa2048' -k
"${KERNEL_SIGNING_DIR}" -n "$b" \
-r conf $dtb
done
I doubt that old patch applies nowadays, I've only forward-ported it to
2020.04 internally.
As to Simon's old question of whether it could be done in mkimage with a
new flag: I'd really prefer not to, mkimage is already an incoherent
collection of tools that do very different things with different flags.
Having a flag that says "create and sign this FIT image, and as a side
effect update $this dtb $overhere with the corresponding public key
mangled appropriately, oh, and btw, _only_ do that side effect" is a
non-starter.
Rasmus
next prev parent reply other threads:[~2021-08-02 9:37 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <25743c08c4b34f9791e39e687399f802@kaspersky.com>
[not found] ` <CAPnjgZ2BSCMcN=-3Vr4wcgZgtB5ExdAxDPE2yfQvT5WJTVajbg@mail.gmail.com>
2021-07-30 17:34 ` U-boot Roman Kopytin
2021-07-30 17:50 ` U-boot Michael Nazzareno Trimarchi
2021-07-31 3:34 ` U-boot Roman Kopytin
2021-07-31 6:51 ` U-boot Thomas Perrot
2021-07-31 8:26 ` U-boot Roman Kopytin
2021-07-31 16:59 ` U-boot Simon Glass
2021-08-02 9:00 ` U-boot Rasmus Villemoes
2021-08-02 9:25 ` U-boot Roman Kopytin
2021-08-02 9:37 ` Rasmus Villemoes [this message]
2021-08-02 9:55 ` U-boot Roman Kopytin
2021-08-02 11:08 ` U-boot Rasmus Villemoes
2021-08-02 11:18 ` U-boot Roman Kopytin
2021-08-02 12:35 ` U-boot Roman Kopytin
2021-08-02 19:20 ` U-boot Simon Glass
[not found] ` <4ba7d9814f544d56b32589e86a5e0617@kaspersky.com>
2021-11-10 19:37 ` U-boot Simon Glass
2005-11-16 0:15 U-Boot mcnernbm
2005-11-16 1:06 ` U-Boot Wolfgang Denk
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=0e75f275-d661-7b75-6da8-91ecec53d78c@prevas.dk \
--to=rasmus.villemoes@prevas.dk \
--cc=Roman.Kopytin@kaspersky.com \
--cc=alex.kiernan@gmail.com \
--cc=michael@amarulasolutions.com \
--cc=sjg@chromium.org \
--cc=thomas.perrot@bootlin.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 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.