From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: Stable releases v2025.09.3 and v2026.03.1
Date: Tue, 17 Mar 2026 15:20:21 +0100 [thread overview]
Message-ID: <abljJRMecNdejSD0@pengutronix.de> (raw)
Hi All,
I have just made two stable releases, both driven by the recently fixed
FIT image vulnerability. The original fix had an issue where we checked
the hashed-nodes property against the nodes-to-hash we extract from the
FIT image structure. It turned out the check was too strict, both should
contain the same nodes, but the order doesn't matter.
v2026.03.1 has this check relaxed and now boots certain valid FIT images
that v2026.03.0 rejected.
v2025.09.3 has both fixes included.
Sascha
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
reply other threads:[~2026-03-17 14:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=abljJRMecNdejSD0@pengutronix.de \
--to=s.hauer@pengutronix.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