From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Sourabh Jain" <sourabhjain@linux.ibm.com>,
"Aditya Gupta" <adityag@linux.ibm.com>
Subject: Re: [PATCH] tests/functional: Enforce sha256 as hashsum algorithm for all tests
Date: Wed, 21 Jan 2026 10:25:50 +0000 [thread overview]
Message-ID: <aXCprhqlW6EJ1xkD@redhat.com> (raw)
In-Reply-To: <20260121101957.82477-1-thuth@redhat.com>
On Wed, Jan 21, 2026 at 11:19:57AM +0100, Thomas Huth wrote:
> From: Thomas Huth <thuth@redhat.com>
>
> The functional testing framework currently supports both, sha256
> and sha512 as hashsums for the assets. However, all but one test
> currently only use sha256, which should also be sufficient according
> to the current security standards. Having two algorithms around already
> caused some confusion (e.g. the clean_functional_cache.py script only
> supports sha256 right now), so standardize now on enforcing sha256
> before more tests use a mix of the two algorithms.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> tests/functional/ppc64/test_fadump.py | 4 +---
> tests/functional/qemu_test/asset.py | 4 +---
> 2 files changed, 2 insertions(+), 6 deletions(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2026-01-21 10:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-21 10:19 [PATCH] tests/functional: Enforce sha256 as hashsum algorithm for all tests Thomas Huth
2026-01-21 10:25 ` Daniel P. Berrangé [this message]
2026-01-21 23:34 ` Richard Henderson
2026-01-22 17:32 ` Aditya Gupta
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=aXCprhqlW6EJ1xkD@redhat.com \
--to=berrange@redhat.com \
--cc=adityag@linux.ibm.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=sourabhjain@linux.ibm.com \
--cc=thuth@redhat.com \
/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.