From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 0/2] Change QEMU crypto hash implementation
Date: Mon, 27 Jun 2016 10:37:45 +0100 [thread overview]
Message-ID: <20160627093745.GF12067@redhat.com> (raw)
In-Reply-To: <1464799972-31095-1-git-send-email-berrange@redhat.com>
On Wed, Jun 01, 2016 at 05:52:50PM +0100, Daniel P. Berrange wrote:
> 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
I'd love some comments if anyone wants to review this, otherwise I'll
submit a pull request for it in a day or two.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
prev parent reply other threads:[~2016-06-27 9:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-01 16:52 [Qemu-devel] [PATCH 0/2] Change QEMU crypto hash implementation Daniel P. Berrange
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 ` Daniel P. Berrange [this message]
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=20160627093745.GF12067@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 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.