From: "Richard W.M. Jones" <rjones@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v2] crypto: Implement TLS Pre-Shared Keys (PSK).
Date: Tue, 26 Jun 2018 11:25:53 +0100 [thread overview]
Message-ID: <20180626102554.23290-1-rjones@redhat.com> (raw)
v1 was here:
https://lists.nongnu.org/archive/html/qemu-devel/2018-06/threads.html#07252
For v2:
- Added documentation as suggested by Dan B.
- Fixed a backwards test of creds->username which slipped into the
previous version by accident because I was fiddling around with the
code after I'd tested it but before posting it. This version
actually works.
Note also there is an nbdkit patch:
https://www.redhat.com/archives/libguestfs/2018-June/thread.html#00121
nbdkit has an automated test that qemu TLS-PSK (NBD client)
interoperates with nbdkit (NBD server), so we can be confident that
the client functionality will receive continuous testing in future.
Rich.
next reply other threads:[~2018-06-26 10:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-26 10:25 Richard W.M. Jones [this message]
2018-06-26 10:25 ` [Qemu-devel] [PATCH v2] crypto: Implement TLS Pre-Shared Keys (PSK) Richard W.M. Jones
2018-06-27 12:21 ` Daniel P. Berrangé
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=20180626102554.23290-1-rjones@redhat.com \
--to=rjones@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).