From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/2] Change QEMU crypto hash implementation
Date: Wed, 1 Jun 2016 17:52:50 +0100 [thread overview]
Message-ID: <1464799972-31095-1-git-send-email-berrange@redhat.com> (raw)
This series changes the QEMU crypto hash implementation to
use gcrypt/nettle directly instead of using gnutls abstraction.
This then lets us support several more hash algorithms that
gnutls does not expose itself. This is useful for LUKS block
driver compatibility with dm-crypt.
Daniel P. Berrange (2):
crypto: switch hash code to use nettle/gcrypt directly
crypto: implement sha224, sha384, sha512 and ripemd160 hashes
configure | 14 -----
crypto/Makefile.objs | 3 +
crypto/hash-gcrypt.c | 110 +++++++++++++++++++++++++++++++++
crypto/hash-nettle.c | 155 +++++++++++++++++++++++++++++++++++++++++++++++
crypto/hash-stub.c | 41 +++++++++++++
crypto/hash.c | 109 ++-------------------------------
qapi/crypto.json | 6 +-
tests/Makefile | 2 +-
tests/test-crypto-hash.c | 53 +++++++++++++++-
9 files changed, 370 insertions(+), 123 deletions(-)
create mode 100644 crypto/hash-gcrypt.c
create mode 100644 crypto/hash-nettle.c
create mode 100644 crypto/hash-stub.c
--
2.5.5
next reply other threads:[~2016-06-01 16:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 16:52 Daniel P. Berrange [this message]
2016-06-01 16:52 ` [Qemu-devel] [PATCH 1/2] crypto: switch hash code to use nettle/gcrypt directly Daniel P. Berrange
2016-06-01 16:52 ` [Qemu-devel] [PATCH 2/2] crypto: implement sha224, sha384, sha512 and ripemd160 hashes Daniel P. Berrange
2016-06-27 9:37 ` [Qemu-devel] [PATCH 0/2] Change QEMU crypto hash implementation Daniel P. Berrange
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=1464799972-31095-1-git-send-email-berrange@redhat.com \
--to=berrange@redhat.com \
--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).