qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 0/4] Qcrypto next patches
Date: Tue, 24 Jul 2018 17:43:47 +0100	[thread overview]
Message-ID: <20180724164351.7293-1-berrange@redhat.com> (raw)

The following changes since commit 3bae150448dbd888a480f892ebbf01caec0d8329:

  Merge remote-tracking branch 'remotes/stefanha/tags/block-pull-request' into staging (2018-07-24 15:26:01 +0100)

are available in the Git repository at:

  https://github.com/berrange/qemu tags/qcrypto-next-pull-request

for you to fetch changes up to db0a8c70f25fe497c4b786d8edac063daa744c0d:

  tests: fix TLS handshake failure with TLS 1.3 (2018-07-24 17:36:12 +0100)

----------------------------------------------------------------
Fix unit test compatibility with TLS 1.3

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

Daniel P. Berrangé (4):
  tests: call qcrypto_init instead of gnutls_global_init
  tests: don't silence error reporting for all tests
  tests: use error_abort in places expecting errors
  tests: fix TLS handshake failure with TLS 1.3

 include/crypto/init.h            |  2 +
 stubs/error-printf.c             |  3 +-
 tests/crypto-tls-x509-helpers.c  |  3 +-
 tests/test-crypto-tlscredsx509.c | 11 +----
 tests/test-crypto-tlssession.c   | 80 ++++++++++++--------------------
 tests/test-io-channel-tls.c      | 24 ++++------
 tests/test-vmstate.c             |  2 +
 7 files changed, 49 insertions(+), 76 deletions(-)

-- 
2.17.1

             reply	other threads:[~2018-07-24 16:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-24 16:43 Daniel P. Berrangé [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-24 16:44 [Qemu-devel] [PULL 0/4] Qcrypto next patches Daniel P. Berrangé
2018-07-24 19:16 ` 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=20180724164351.7293-1-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).