From: Peter Korsgaard <peter@korsgaard.com>
To: Fiona Klute via buildroot <buildroot@buildroot.org>
Cc: Fiona Klute <fiona.klute@gmx.de>
Subject: Re: [Buildroot] [PATCH 1/1] support/download: enforce BR2_DOWNLOAD_FORCE_CHECK_HASHES=y for missing hash files
Date: Sun, 18 Oct 2026 14:42:55 +0200 [thread overview]
Message-ID: <877bjf2n8w.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20261018120941.1476904-1-fiona.klute@gmx.de> (Fiona Klute via buildroot's message of "Sun, 18 Oct 2026 14:09:40 +0200")
>>>>> "Fiona" == Fiona Klute via buildroot <buildroot@buildroot.org> writes:
> BR2_DOWNLOAD_FORCE_CHECK_HASHES=y is supposed to make the build fail
> if any download cannot be successfully verified against a known
> hash. However, support/download/check-hash would only warn if there
> was no hash file at all for the package in question, and allow the
> build to continue.
> This is a security fix and should be backported to all stable
> branches.
> Signed-off-by: Fiona Klute <fiona.klute@gmx.de>
Committed, thanks.
Maybe we need some more download tests?
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2026-10-18 12:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-18 12:09 [Buildroot] [PATCH 1/1] support/download: enforce BR2_DOWNLOAD_FORCE_CHECK_HASHES=y for missing hash files Fiona Klute via buildroot
2026-10-18 12:42 ` Peter Korsgaard [this message]
2026-10-23 13:20 ` Raphaël Mélotte via buildroot
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=877bjf2n8w.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=fiona.klute@gmx.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 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.