From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Richard Jones" <rjones@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [Qemu-devel] [PULL 0/1] Qcrypto next patches
Date: Tue, 3 Jul 2018 13:05:11 +0100 [thread overview]
Message-ID: <20180703120512.31648-1-berrange@redhat.com> (raw)
The following changes since commit 9b75dcb15f562577a937ae01f324946513586e59:
Merge remote-tracking branch 'remotes/ericb/tags/pull-nbd-2018-07-02' into staging (2018-07-03 10:47:02 +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 e1a6dc91ddb55ef77a705b62b6e62634631fd57d:
crypto: Implement TLS Pre-Shared Keys (PSK). (2018-07-03 13:04:38 +0100)
----------------------------------------------------------------
Add support for PSK credentials with TLS
----------------------------------------------------------------
Richard W.M. Jones (1):
crypto: Implement TLS Pre-Shared Keys (PSK).
crypto/Makefile.objs | 1 +
crypto/tlscredspsk.c | 308 +++++++++++++++++++++++++++++++++
crypto/tlssession.c | 56 +++++-
crypto/trace-events | 3 +
include/crypto/tlscredspsk.h | 106 ++++++++++++
qemu-doc.texi | 37 ++++
qemu-options.hx | 24 +++
tests/Makefile.include | 4 +-
tests/crypto-tls-psk-helpers.c | 50 ++++++
tests/crypto-tls-psk-helpers.h | 29 ++++
tests/test-crypto-tlssession.c | 179 ++++++++++++++++---
11 files changed, 774 insertions(+), 23 deletions(-)
create mode 100644 crypto/tlscredspsk.c
create mode 100644 include/crypto/tlscredspsk.h
create mode 100644 tests/crypto-tls-psk-helpers.c
create mode 100644 tests/crypto-tls-psk-helpers.h
--
2.17.1
next reply other threads:[~2018-07-03 12:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 12:05 Daniel P. Berrangé [this message]
2018-07-03 12:05 ` [Qemu-devel] [PULL 1/1] crypto: Implement TLS Pre-Shared Keys (PSK) Daniel P. Berrangé
2018-07-04 6:27 ` [Qemu-devel] [PULL 0/1] Qcrypto next 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=20180703120512.31648-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.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 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).