From: Alejandro Zeise <alejandro.zeise@seagate.com>
To: qemu-arm@nongnu.org
Cc: qemu-devel@nongnu.org, alejandro.zeise@seagate.com, clg@kaod.org,
peter.maydell@linaro.org, berrange@redhat.com
Subject: [PATCH 0/2] hw/misc/aspeed_hace: Fix SG Accumulative Hash Calculations
Date: Mon, 22 Jul 2024 20:15:22 +0000 [thread overview]
Message-ID: <20240722201524.822730-1-alejandro.zeise@seagate.com> (raw)
The goal of this patch series is to fix accumulative hashing support in the
Aspeed HACE module. The issue that stemmed this patch was a failure to boot an
OpenBMC image using the "ast2600-evb" machine. The U-boot
2019.04 loader failed to verify image hashes.
These incorrect image hashes given by the HACE to the U-boot guest are due to
an oversight in the HACE module. Previously when operating in
scatter-gather accumulative mode, the HACE would cache the address provided by
the guest which contained the source data. However, there was no deep copy,
so when HACE generated the digest upon the reception of the final accumulative chunk
the digest was incorrect, as the addresses provided had their regions overwritten
by that time.
This fix consists of two main steps:
* Add an accumulative hashing function to the qcrypto library
* Modify the HACE module to use the accumulative hashing functions
All the crypto library backends (nettle, gnutls, etc.) support accumulative hashing,
so it was trivial to create wrappers for those functions.
Alejandro Zeise (2):
crypto: add support for accumulative hashing
hw/misc/aspeed_hace: Fix SG Accumulative hashing
crypto/hash-gcrypt.c | 105 ++++++++++++++++++++++++++++++++++
crypto/hash-glib.c | 89 ++++++++++++++++++++++++++++
crypto/hash-gnutls.c | 82 ++++++++++++++++++++++++++
crypto/hash-nettle.c | 93 ++++++++++++++++++++++++++++++
crypto/hash.c | 42 ++++++++++++++
crypto/hashpriv.h | 11 ++++
hw/misc/aspeed_hace.c | 91 +++++++++++++++--------------
include/crypto/hash.h | 65 +++++++++++++++++++++
include/hw/misc/aspeed_hace.h | 4 ++
9 files changed, 538 insertions(+), 44 deletions(-)
--
2.34.1
next reply other threads:[~2024-07-22 21:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-22 20:15 Alejandro Zeise [this message]
2024-07-22 20:15 ` [PATCH 1/2] crypto: add support for accumulative hashing Alejandro Zeise
2024-07-22 20:15 ` [PATCH 2/2] hw/misc/aspeed_hace: Fix SG Accumulative hashing Alejandro Zeise
2024-07-22 21:39 ` Cédric Le Goater
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=20240722201524.822730-1-alejandro.zeise@seagate.com \
--to=alejandro.zeise@seagate.com \
--cc=berrange@redhat.com \
--cc=clg@kaod.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).