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>,
	"Longpeng(Mike)" <longpeng2@huawei.com>,
	"Daniel P . Berrange" <berrange@redhat.com>
Subject: [Qemu-devel] [PULL v2 3/8] configure: add CONFIG_GCRYPT_HMAC item
Date: Thu, 22 Dec 2016 10:47:35 +0000	[thread overview]
Message-ID: <20161222104740.19606-4-berrange@redhat.com> (raw)
In-Reply-To: <20161222104740.19606-1-berrange@redhat.com>

From: "Longpeng(Mike)" <longpeng2@huawei.com>

This item will be used for support libcrypt-backed HMAC algorithms.

Support for hmac has been added in Libgcrypt 1.6.0, but we cannot
use pkg-config to get libcrypt's version. However we can make a
in configure to know whether current libcrypt support hmac.

Signed-off-by: Longpeng(Mike) <longpeng2@huawei.com>
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
---
 configure | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)

diff --git a/configure b/configure
index 3770d7c..f30aa1b 100755
--- a/configure
+++ b/configure
@@ -313,6 +313,7 @@ gnutls_rnd=""
 nettle=""
 nettle_kdf="no"
 gcrypt=""
+gcrypt_hmac="no"
 gcrypt_kdf="no"
 vte=""
 virglrenderer=""
@@ -2417,6 +2418,19 @@ EOF
         if compile_prog "$gcrypt_cflags" "$gcrypt_libs" ; then
             gcrypt_kdf=yes
         fi
+
+        cat > $TMPC << EOF
+#include <gcrypt.h>
+int main(void) {
+  gcry_mac_hd_t handle;
+  gcry_mac_open(&handle, GCRY_MAC_HMAC_MD5,
+                GCRY_MAC_FLAG_SECURE, NULL);
+  return 0;
+}
+EOF
+        if compile_prog "$gcrypt_cflags" "$gcrypt_libs" ; then
+            gcrypt_hmac=yes
+        fi
     else
         if test "$gcrypt" = "yes"; then
             feature_not_found "gcrypt" "Install gcrypt devel"
@@ -5387,6 +5401,9 @@ if test "$gnutls_rnd" = "yes" ; then
 fi
 if test "$gcrypt" = "yes" ; then
   echo "CONFIG_GCRYPT=y" >> $config_host_mak
+  if test "$gcrypt_hmac" = "yes" ; then
+    echo "CONFIG_GCRYPT_HMAC=y" >> $config_host_mak
+  fi
   if test "$gcrypt_kdf" = "yes" ; then
     echo "CONFIG_GCRYPT_KDF=y" >> $config_host_mak
   fi
-- 
2.9.3

  parent reply	other threads:[~2016-12-22 10:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-22 10:47 [Qemu-devel] [PULL v2 0/8] Merge qcrypto 2016-12-21 Daniel P. Berrange
2016-12-22 10:47 ` [Qemu-devel] [PULL v2 1/8] cipher: fix leak on initialization error Daniel P. Berrange
2016-12-22 10:47 ` [Qemu-devel] [PULL v2 2/8] crypto: add 3des-ede support when using libgcrypt/nettle Daniel P. Berrange
2016-12-22 10:47 ` Daniel P. Berrange [this message]
2016-12-22 10:47 ` [Qemu-devel] [PULL v2 4/8] crypto: add HMAC algorithms framework Daniel P. Berrange
2016-12-22 10:47 ` [Qemu-devel] [PULL v2 5/8] crypto: support HMAC algorithms based on libgcrypt Daniel P. Berrange
2016-12-22 10:47 ` [Qemu-devel] [PULL v2 6/8] crypto: support HMAC algorithms based on glib Daniel P. Berrange
2016-12-22 10:47 ` [Qemu-devel] [PULL v2 7/8] crypto: support HMAC algorithms based on nettle Daniel P. Berrange
2016-12-22 10:47 ` [Qemu-devel] [PULL v2 8/8] crypto: add HMAC algorithms testcases Daniel P. Berrange
2016-12-22 19:23 ` [Qemu-devel] [PULL v2 0/8] Merge qcrypto 2016-12-21 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=20161222104740.19606-4-berrange@redhat.com \
    --to=berrange@redhat.com \
    --cc=longpeng2@huawei.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.