From: Rasmus Villemoes <rasmus.villemoes@prevas.dk>
To: Simon Glass <sjg@chromium.org>,
Roman Kopytin <Roman.Kopytin@kaspersky.com>
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:00:06 +0200 [thread overview]
Message-ID: <11ae1091-bf2d-800f-d513-840119655fb2@prevas.dk> (raw)
In-Reply-To: <CAPnjgZ3BUW2iw+B1v=CC2PvOa9ur_VGm_k3FBQju01jFNkVz+A@mail.gmail.com>
On 31/07/2021 18.59, Simon Glass wrote:
> Hi Roman,
>
> On Sat, 31 Jul 2021 at 02:26, Roman Kopytin <Roman.Kopytin@kaspersky.com> wrote:
>>
>> Thank, but my question was about adding of the public key to dtb file without private key. We won't have private key in our side.
>
> (please try not to top-post on the mailing list)
>
> Presumably this means that you know what the public key is, so one
> option is to manually add it to the dtb, e.g. in a u-boot.dtsi file
> for your board. You can see the format of it in the documentation, or
> just copy what is there when you do the signing.
>
I sent
https://lore.kernel.org/u-boot/20200211094818.14219-3-rasmus.villemoes@prevas.dk/
1.5 years ago. Roman, is it something like that you need? We've used
that patch/tool internally ever since.
> Another option would be to use 'fdtput' to add the various fields in
> the dtb after building.
Yes, but that, or the .dtsi approach, requires figuring just exactly
what those fields are supposed to be. And even if one could "reverse
engineer" that and implement the math separately in another tool, it's
much better to utilize the same code which "mkimage proper" would use,
since there's less risk of messing up endianness etc., and only one
place to fix bugs.
Rasmus
next prev parent reply other threads:[~2021-08-02 9:00 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 ` Rasmus Villemoes [this message]
2021-08-02 9:25 ` U-boot Roman Kopytin
2021-08-02 9:37 ` U-boot Rasmus Villemoes
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=11ae1091-bf2d-800f-d513-840119655fb2@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.