From: Eric Blake <eblake@redhat.com>
To: "Richard W.M. Jones" <rjones@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-block@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v3] crypto: Implement TLS Pre-Shared Keys (PSK).
Date: Thu, 28 Jun 2018 09:48:22 -0500 [thread overview]
Message-ID: <feac5d6e-9f5c-ee83-1a8d-3f628d29d620@redhat.com> (raw)
In-Reply-To: <cf457707-eaab-16f9-d1c9-3a3f6423958e@redhat.com>
On 06/28/2018 09:42 AM, Eric Blake wrote:
> On 06/28/2018 08:22 AM, Richard W.M. Jones wrote:
>
> In the subject line: most commit summaries don't have a trailing '.'.
>
>> Pre-Shared Keys (PSK) is a simpler mechanism for enabling TLS
>> connections than using certificates. It requires only a simple secret
>> key:
>>
>> $ mkdir -m 0700 /tmp/keys
>> $ psktool -u rjones -p /tmp/keys/keys.psk
>> $ cat /tmp/keys/keys.psk
>>
>> rjones:d543770c15ad93d76443fb56f501a31969235f47e999720ae8d2336f6a13fcbc
>>
>> The key can be secretly shared between clients and servers. Clients
>> must specify the directory containing the "keys.psk" file and a
>> username (defaults to "qemu"). Servers must specify only the
>> directory.
>>
>> Example NBD client:
>>
>> $ qemu-img info \
>> --object
>> tls-creds-psk,id=tls0,dir=/tmp/keys,username=rjones,endpoint=client \
>> --image-opts \
>>
>> file.driver=nbd,file.host=localhost,file.port=10809,file.tls-creds=tls0,file.export=/
>
> Otherwise, I'm not spotting problems, but as it touches crypto, I'd also
> get Dan's review.
>
Because of the immediate use for NBD, I'm willing to take this through
the NBD tree if Dan gives a review or ack. Or, if Dan wants it through
the crypto tree (and my minor nits are addressed),
Acked-by: Eric Blake <eblake@redhat.com>
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3266
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2018-06-28 14:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 13:22 [Qemu-devel] [PATCH v3] crypto: Implement TLS Pre-Shared Keys (PSK) Richard W.M. Jones
2018-06-28 13:22 ` Richard W.M. Jones
2018-06-28 14:42 ` Eric Blake
2018-06-28 14:48 ` Eric Blake [this message]
2018-06-28 15:54 ` Richard W.M. Jones
2018-06-28 15:58 ` Daniel P. Berrangé
2018-06-28 16:06 ` Daniel P. Berrangé
2018-06-28 16:51 ` Richard W.M. Jones
2018-06-28 17:13 ` 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=feac5d6e-9f5c-ee83-1a8d-3f628d29d620@redhat.com \
--to=eblake@redhat.com \
--cc=qemu-block@nongnu.org \
--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).