From: Lukasz Majewski <lukma@denx.de>
To: u-boot@lists.denx.de
Subject: Sourcing a signed boot script
Date: Thu, 5 Dec 2019 23:14:46 +0100 [thread overview]
Message-ID: <20191205231446.072cd172@jawa> (raw)
In-Reply-To: <CAMfw5YrfUBKyR1g+52OwfDjBMU4ZbVchp1aDGuQn0qh--mKRdA@mail.gmail.com>
Hi Diego,
> Hi,
>
> I would like to ask if it is possible to source a script after
> verifying its signature.
>
> Currently I've been able to source a script from a signed FIT image,
> before doing "bootm", with:
> source <addr>:<name>
> But this way the signature is not checked yet, so the script cannot
> be trusted.
>
> According to the docs[1] it seems that it's not possible yet to verify
> a FIT image signature without also booting the corresponding image. Is
> that right?
You can look into the "spl" command, which does the FIT parsing (to
prepare data for falcon mode booting).
You may want to re-use such "dry-run" feature to verify the signature,
extract the script and use it.
(And yes, I don't think that checking the signature for script works
out of the box).
>
>
> [1]
> https://gitlab.denx.de/u-boot/u-boot/blob/v2019.10/doc/uImage.FIT/signature.txt#L580
>
> Thank you,
> Diego Rondini
Best regards,
Lukasz Majewski
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-59 Fax: (+49)-8142-66989-80 Email: lukma at denx.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20191205/a967bc2c/attachment.sig>
next prev parent reply other threads:[~2019-12-05 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-05 17:09 Sourcing a signed boot script Diego Rondini
2019-12-05 22:14 ` Lukasz Majewski [this message]
2019-12-06 14:47 ` Diego Rondini
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=20191205231446.072cd172@jawa \
--to=lukma@denx.de \
--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