All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"Daniel P. Berrange" <berrange@redhat.com>
Subject: [Qemu-devel] [PULL v1 0/7] Merge qcrypto 2016/12/21
Date: Wed, 21 Dec 2016 14:35:34 +0000	[thread overview]
Message-ID: <20161221143541.9260-1-berrange@redhat.com> (raw)

The following changes since commit 82ecffa8c050bf5bbc13329e9b65eac1caa5b55c:

  Open 2.9 development tree (2016-12-20 16:20:16 +0000)

are available in the git repository at:

  git://github.com/berrange/qemu tags/pull-qcrypto-2016-12-21-1

for you to fetch changes up to d1c7d71dcec794de02838cbb96a6f99fee13d8a5:

  crypto: add HMAC algorithms testcases (2016-12-21 14:26:26 +0000)

----------------------------------------------------------------
Merge qcrypto 2016/12/21 v1

----------------------------------------------------------------

Longpeng(Mike) (6):
  crypto: add 3des-ede support when using libgcrypt/nettle
  crypto: add HMAC algorithms framework
  crypto: support HMAC algorithms based on libgcrypt
  crypto: support HMAC algorithms based on glib
  crypto: support HMAC algorithms based on nettle
  crypto: add HMAC algorithms testcases

Marc-André Lureau (1):
  cipher: fix leak on initialization error

 crypto/Makefile.objs       |   4 +
 crypto/cipher-gcrypt.c     |   6 +
 crypto/cipher-nettle.c     |  42 ++++++-
 crypto/cipher.c            |   7 +-
 crypto/hmac-gcrypt.c       | 152 ++++++++++++++++++++++++++
 crypto/hmac-glib.c         | 166 ++++++++++++++++++++++++++++
 crypto/hmac-nettle.c       | 175 +++++++++++++++++++++++++++++
 crypto/hmac.c              |  72 ++++++++++++
 crypto/hmac.h              | 166 ++++++++++++++++++++++++++++
 qapi/crypto.json           |   3 +-
 tests/Makefile.include     |   2 +
 tests/test-crypto-cipher.c | 119 ++++++++++++++++++++
 tests/test-crypto-hmac.c   | 266 +++++++++++++++++++++++++++++++++++++++++++++
 13 files changed, 1174 insertions(+), 6 deletions(-)
 create mode 100644 crypto/hmac-gcrypt.c
 create mode 100644 crypto/hmac-glib.c
 create mode 100644 crypto/hmac-nettle.c
 create mode 100644 crypto/hmac.c
 create mode 100644 crypto/hmac.h
 create mode 100644 tests/test-crypto-hmac.c

-- 
2.9.3

             reply	other threads:[~2016-12-21 14:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 14:35 Daniel P. Berrange [this message]
2016-12-21 14:35 ` [Qemu-devel] [PULL v1 1/7] cipher: fix leak on initialization error Daniel P. Berrange
2016-12-21 14:35 ` [Qemu-devel] [PULL v1 2/7] crypto: add 3des-ede support when using libgcrypt/nettle Daniel P. Berrange
2016-12-21 14:35 ` [Qemu-devel] [PULL v1 3/7] crypto: add HMAC algorithms framework Daniel P. Berrange
2016-12-22  1:07   ` Longpeng (Mike)
2016-12-22  9:26     ` Daniel P. Berrange
2016-12-21 14:35 ` [Qemu-devel] [PULL v1 4/7] crypto: support HMAC algorithms based on libgcrypt Daniel P. Berrange
2016-12-21 14:35 ` [Qemu-devel] [PULL v1 5/7] crypto: support HMAC algorithms based on glib Daniel P. Berrange
2016-12-21 14:35 ` [Qemu-devel] [PULL v1 6/7] crypto: support HMAC algorithms based on nettle Daniel P. Berrange
2016-12-21 14:35 ` [Qemu-devel] [PULL v1 7/7] crypto: add HMAC algorithms testcases 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=20161221143541.9260-1-berrange@redhat.com \
    --to=berrange@redhat.com \
    --cc=peter.maydell@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 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.