From: Sascha Silbe <silbe@linux.vnet.ibm.com>
To: Alberto Garcia <berto@igalia.com>, Fam Zheng <famz@redhat.com>,
qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] quorum: Only compile when supported
Date: Tue, 05 Jul 2016 11:15:55 +0200 [thread overview]
Message-ID: <87eg78la2c.fsf@oc4731375738.ibm.com> (raw)
In-Reply-To: <w51furojy1i.fsf@maestria.local.igalia.com>
Dear Alberto,
Alberto Garcia <berto@igalia.com> writes:
> On Tue 05 Jul 2016 09:58:25 AM CEST, Sascha Silbe wrote:
>
>> The quorum driver needs SHA256 which was introduced in gnutls 2.11.1.
>
> Are you sure about that?
>
> * Version 1.7.4 (released 2007-02-05)
>
> [...]
>
> ** API and ABI modifications:
> GNUTLS_MAC_SHA256,
[...]
You are right, I misinterpreted the gnutls 2.11.1 NEWS entry. It added
the RSA_NULL_SHA256 cipher suite, not the SHA256 hash algorithm.
So the existing configure check is good enough, no need to bump the
required gnutls version.
Sascha
--
Softwareentwicklung Sascha Silbe, Niederhofenstraße 5/1, 71229 Leonberg
https://se-silbe.de/
USt-IdNr. DE281696641
next prev parent reply other threads:[~2016-07-05 9:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 1:47 [Qemu-devel] [PATCH] quorum: Only compile when supported Fam Zheng
2016-06-28 8:17 ` Alberto Garcia
2016-07-02 12:36 ` Max Reitz
2016-07-04 11:43 ` Alberto Garcia
2016-07-05 7:03 ` Fam Zheng
2016-07-05 7:58 ` Sascha Silbe
2016-07-05 8:11 ` Fam Zheng
2016-07-05 8:20 ` Alberto Garcia
2016-07-05 9:15 ` Sascha Silbe [this message]
2016-07-05 8:45 ` Daniel P. Berrange
2016-07-05 8:57 ` Fam Zheng
2016-07-05 9:35 ` Daniel P. Berrange
2016-07-06 0:56 ` Fam Zheng
2016-07-05 9:18 ` Alberto Garcia
2016-07-05 9:26 ` Daniel P. Berrange
2016-07-05 10:05 ` 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=87eg78la2c.fsf@oc4731375738.ibm.com \
--to=silbe@linux.vnet.ibm.com \
--cc=berto@igalia.com \
--cc=famz@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.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.