From: Philippe REYNES <philippe.reynes@softathome.com>
To: u-boot@lists.denx.de
Subject: U-Boot FIT Signature Verification
Date: Wed, 16 Sep 2020 22:01:21 +0200 (CEST) [thread overview]
Message-ID: <1131280458.1110639.1600286481334.JavaMail.zimbra@softathome.com> (raw)
In-Reply-To: <5075840b-acb3-5146-17ff-098dd739ee68@gmx.de>
Hi Heinrich,
> On 9/11/20 7:26 PM, Andrii Voloshyn wrote:
>> Hi there,
>>
>> Does U-boot take into account certificate expiration date when verifying signed
>> images in FIT? In other words, is date stored along with the public key in DTB
>> file?
>>
>> Cheers,
>> Andy
>>
>
> Hello Philippe,
>
> looking at padding_pkcs_15_verify() in lib/rsa/rsa-verify.c I cannot
> find a comparison of the date on which an image was signed with the
> expiry date of the certificate. Shouldn't there be a check? Or did I
> simply look into the wrong function?
This function only check the padding using the algorithm pkcs-1.5 as
defined here : https://tools.ietf.org/html/rfc3447#section-9.2
It doesn't check the certificate validity.
I don't remember to have see a date checked in the signature process.
If all informations are (or may be) available at runtime, we may
add it.
> Best regards
>
> Heinrich
Best regards,
Philippe
next prev parent reply other threads:[~2020-09-16 20:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 17:26 U-Boot FIT Signature Verification Andrii Voloshyn
2020-09-15 23:19 ` Heinrich Schuchardt
2020-09-16 8:13 ` AKASHI Takahiro
2020-09-16 11:14 ` Heinrich Schuchardt
2020-09-16 11:40 ` Joakim Tjernlund
2020-09-16 11:55 ` Heinrich Schuchardt
2020-09-16 12:05 ` Joakim Tjernlund
2020-09-16 12:44 ` Heinrich Schuchardt
2020-09-16 19:54 ` Tom Rini
2020-09-17 5:33 ` takahiro.akashi at linaro.org
2020-09-17 5:57 ` takahiro.akashi at linaro.org
2020-09-17 5:26 ` AKASHI Takahiro
2020-09-16 20:01 ` Philippe REYNES [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-09-16 15:31 REITHER Robert - Contractor
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=1131280458.1110639.1600286481334.JavaMail.zimbra@softathome.com \
--to=philippe.reynes@softathome.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox