From: Sascha Hauer <s.hauer@pengutronix.de>
To: Kai Che <Kai.Che@mixed-mode.de>
Cc: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: Re: issues verifying FIT image signature
Date: Wed, 7 Nov 2018 09:01:26 +0100 [thread overview]
Message-ID: <20181107080126.k37o63mf6qrnmx4t@pengutronix.de> (raw)
In-Reply-To: <1541171808732.30346@mixed-mode.de>
Hi Kai,
On Fri, Nov 02, 2018 at 03:16:44PM +0000, Kai Che wrote:
> Hi all,
>
> I'm trying to verify the signature of a FIT image in barebox.
>
> I created the FIT image with the following .its file:
>
> ...
> configurations {
> default = "config@1";
> config@1 {
> description = "Boot Raspian kernel";
> kernel = "kernel";
> fdt = "fdt-1";
> signature@1 {
> algo = "sha256,rsa2048";
> key-name-hint = "dev";
> sign-images = "fdt", "kernel";
> ...
>
> Verifying the Hashes for the kernel and fdt-1 works fine ("hash OK"
> for both images) , but when I try to verify the signature I get the
> follwoing error:
>
> ERROR: FIT: hashed-strings start not found in /configurations/config@1/signature@1
>
> I could follow the error back to the fit_verify_signature function in
> /common/image-fit.c file, but I don't understand what is causing the
> error.
>
> Is the function looking for a string called "hashed-strings" in the
> FIT image file? I checked the .fit file (with hexdump) and I could
> only find the string "hash@1" which barebox uses to verify the
> signature.
No idea what went wrong. Which options did you pass to mkimage?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2018-11-07 8:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 15:16 Kai Che
2018-11-07 8:01 ` Sascha Hauer [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=20181107080126.k37o63mf6qrnmx4t@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=Kai.Che@mixed-mode.de \
--cc=barebox@lists.infradead.org \
/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