From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Vladimir Sementsov-Ogievskiy" <vsementsov@virtuozzo.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-block@nongnu.org, "Juan Quintela" <quintela@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
"Max Reitz" <mreitz@redhat.com>,
"Gerd Hoffmann" <kraxel@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Eric Blake" <eblake@redhat.com>
Subject: [PULL 0/7] crypto patches
Date: Wed, 30 Jun 2021 12:56:05 +0100 [thread overview]
Message-ID: <20210630115612.827664-1-berrange@redhat.com> (raw)
The following changes since commit 13d5f87cc3b94bfccc501142df4a7b12fee3a6e7:
Merge remote-tracking branch 'remotes/rth-gitlab/tags/pull-axp-20210628' into staging (2021-06-29 10:02:42 +0100)
are available in the Git repository at:
https://gitlab.com/berrange/qemu tags/tls-deps-pull-request
for you to fetch changes up to 678bcc3c2cf22262d0a72b52da57737c4a40e040:
crypto: Make QCryptoTLSCreds* structures private (2021-06-29 18:30:24 +0100)
----------------------------------------------------------------
Hide build time dependancy on gnutls fom non-crypto code
----------------------------------------------------------------
Philippe Mathieu-Daudé (7):
crypto/tlscreds: Introduce qcrypto_tls_creds_check_endpoint() helper
block/nbd: Use qcrypto_tls_creds_check_endpoint()
qemu-nbd: Use qcrypto_tls_creds_check_endpoint()
chardev/socket: Use qcrypto_tls_creds_check_endpoint()
migration/tls: Use qcrypto_tls_creds_check_endpoint()
ui/vnc: Use qcrypto_tls_creds_check_endpoint()
crypto: Make QCryptoTLSCreds* structures private
block/nbd.c | 6 ++--
blockdev-nbd.c | 6 ++--
chardev/char-socket.c | 18 ++++--------
crypto/tls-cipher-suites.c | 7 +++++
crypto/tlscreds.c | 12 ++++++++
crypto/tlscredsanon.c | 2 ++
crypto/tlscredspriv.h | 45 ++++++++++++++++++++++++++++++
crypto/tlscredspsk.c | 2 ++
crypto/tlscredsx509.c | 1 +
crypto/tlssession.c | 1 +
include/crypto/tls-cipher-suites.h | 6 ----
include/crypto/tlscreds.h | 30 ++++++++++----------
include/crypto/tlscredsanon.h | 12 --------
include/crypto/tlscredspsk.h | 12 --------
include/crypto/tlscredsx509.h | 10 -------
migration/tls.c | 6 +---
qemu-nbd.c | 19 +++++--------
ui/vnc.c | 7 +++--
18 files changed, 108 insertions(+), 94 deletions(-)
--
2.31.1
next reply other threads:[~2021-06-30 12:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-30 11:56 Daniel P. Berrangé [this message]
2021-06-30 11:56 ` [PULL 1/7] crypto/tlscreds: Introduce qcrypto_tls_creds_check_endpoint() helper Daniel P. Berrangé
2021-06-30 11:56 ` [PULL 2/7] block/nbd: Use qcrypto_tls_creds_check_endpoint() Daniel P. Berrangé
2021-06-30 11:56 ` [PULL 3/7] qemu-nbd: " Daniel P. Berrangé
2021-06-30 11:56 ` [PULL 4/7] chardev/socket: " Daniel P. Berrangé
2021-06-30 11:56 ` [PULL 5/7] migration/tls: " Daniel P. Berrangé
2021-06-30 11:56 ` [PULL 6/7] ui/vnc: " Daniel P. Berrangé
2021-06-30 11:56 ` [PULL 7/7] crypto: Make QCryptoTLSCreds* structures private Daniel P. Berrangé
2021-07-02 10:16 ` [PULL 0/7] crypto patches 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=20210630115612.827664-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=eblake@redhat.com \
--cc=kraxel@redhat.com \
--cc=kwolf@redhat.com \
--cc=marcandre.lureau@redhat.com \
--cc=mreitz@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
--cc=vsementsov@virtuozzo.com \
/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.