From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Eric Blake" <eblake@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Markus Armbruster" <armbru@redhat.com>
Subject: [PULL 0/4] Crypto fixes patches
Date: Tue, 5 Nov 2024 18:41:11 +0000 [thread overview]
Message-ID: <20241105184115.381511-1-berrange@redhat.com> (raw)
The following changes since commit 44a9394b1d272b53306d097d4bc20ff7ad14b159:
Merge tag 'pull-nvme-20241104' of https://gitlab.com/birkelund/qemu into staging (2024-11-05 14:23:22 +0000)
are available in the Git repository at:
https://gitlab.com/berrange/qemu tags/crypto-fixes-pull-request
for you to fetch changes up to a7e42752324a264439bef28da3ee3e2563cf0e16:
crypto: perform runtime check for hash/hmac support in gcrypt (2024-11-05 18:37:18 +0000)
----------------------------------------------------------------
* Remove deprecated 'loaded' property from crypto objects
* Fix error checking of hash function in gcrypt
* Perform runtime check for hash functions in gcrypt
* Add SM3 hash function to pbkdf
----------------------------------------------------------------
Daniel P. Berrangé (3):
crypto: purge 'loaded' property that was not fully removed
crypto: fix error check on gcry_md_open
crypto: perform runtime check for hash/hmac support in gcrypt
liequan che (1):
crypto: Introduce SM3 hash hmac pbkdf algorithm
crypto/hash-gcrypt.c | 9 ++++--
crypto/hash-nettle.c | 14 +++++++++
crypto/hash.c | 3 ++
crypto/hmac-gcrypt.c | 5 ++-
crypto/hmac-nettle.c | 11 +++++++
crypto/pbkdf-gcrypt.c | 6 ++++
crypto/pbkdf-nettle.c | 13 ++++++++
crypto/secret_common.c | 12 --------
crypto/tlscredsanon.c | 35 ---------------------
crypto/tlscredspsk.c | 34 ---------------------
crypto/tlscredsx509.c | 30 ------------------
docs/about/removed-features.rst | 6 ++--
include/crypto/hash.h | 1 +
meson.build | 39 ++++++++++++++++++++++++
qapi/crypto.json | 54 ++++-----------------------------
tests/unit/test-crypto-hash.c | 16 ++++++++++
tests/unit/test-crypto-hmac.c | 8 +++++
tests/unit/test-crypto-pbkdf.c | 16 ++++++++++
18 files changed, 146 insertions(+), 166 deletions(-)
--
2.46.0
next reply other threads:[~2024-11-05 18:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-05 18:41 Daniel P. Berrangé [this message]
2024-11-05 18:41 ` [PULL 1/4] crypto: purge 'loaded' property that was not fully removed Daniel P. Berrangé
2024-11-05 18:41 ` [PULL 2/4] crypto: Introduce SM3 hash hmac pbkdf algorithm Daniel P. Berrangé
2024-11-05 18:41 ` [PULL 3/4] crypto: fix error check on gcry_md_open Daniel P. Berrangé
2024-11-05 18:41 ` [PULL 4/4] crypto: perform runtime check for hash/hmac support in gcrypt Daniel P. Berrangé
2024-11-06 21:27 ` [PULL 0/4] Crypto fixes patches Peter Maydell
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=20241105184115.381511-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=eblake@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=philmd@linaro.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).