All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kai Che <Kai.Che@mixed-mode.de>
To: "barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: issues verifying FIT image signature
Date: Fri, 2 Nov 2018 15:16:44 +0000	[thread overview]
Message-ID: <1541171808732.30346@mixed-mode.de> (raw)

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.

Best regards

Kai


   
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox

             reply	other threads:[~2018-11-02 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02 15:16 Kai Che [this message]
2018-11-07  8:01 ` issues verifying FIT image signature Sascha Hauer

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=1541171808732.30346@mixed-mode.de \
    --to=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 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.