From: Eric Blake <eblake@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: Kevin Wolf <kwolf@redhat.com>,
qemu-block@nongnu.org, Juan Quintela <quintela@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
"Dr. David Alan Gilbert" <dgilbert@redhat.com>,
Max Reitz <mreitz@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v6 1/3] qemu-nbd: add support for authorization of TLS clients
Date: Thu, 28 Feb 2019 12:20:16 -0600 [thread overview]
Message-ID: <75393117-5893-4ca1-f86b-83913a924e53@redhat.com> (raw)
In-Reply-To: <29dfdc31-9e4d-88be-13f0-53e3f33d6800@redhat.com>
On 2/27/19 10:43 AM, Eric Blake wrote:
>> @example
>> qemu-nbd \
>> --object tls-creds-x509,id=tls0,endpoint=server,dir=/path/to/qemutls \
>> - --tls-creds tls0 -t -x subset -p 10810 \
>> + --object 'authz-simple,id=auth0,identity=CN=laptop.example.com,,\
>> + O=Example Org,,L=London,,ST=London,,C=GB' \
>
> A long line may be necessary here, unless the whitespace in the
> identity= parameter inserted by the line continuation is harmless. Long
> lines in man pages are annoying, but even worse is an example that
> copies-and-pastes incorrectly. I may just s/^ *O/O/.
I've just confirmed that whitespace in the identity= parameter is
harmless, via this change:
diff --git i/tests/qemu-iotests/233 w/tests/qemu-iotests/233
index 6adade45353..5e5fe1e8cdb 100755
--- i/tests/qemu-iotests/233
+++ w/tests/qemu-iotests/233
@@ -131,7 +131,8 @@ nbd_server_stop
nbd_server_start_tcp_socket \
--object
tls-creds-x509,dir=${tls_dir}/server1,endpoint=server,id=tls0,verify-peer=yes
\
- --object "authz-simple,identity=CN=localhost,,O=Cthulu Dark Lord
Enterprises client1,,L=R'lyeh,,C=South Pacific,id=authz0" \
+ --object "authz-simple,id=authz0,identity=CN=localhost,, \
+ O=Cthulu Dark Lord Enterprises client1,,L=R'lyeh,,C=South Pacific" \
--tls-authz authz0 \
--tls-creds tls0 \
-f $IMGFMT "$TEST_IMG" 2>> "$TEST_DIR/server.log"
So I'll go ahead and tweak the patch along those lines.
--
Eric Blake, Principal Software Engineer
Red Hat, Inc. +1-919-301-3226
Virtualization: qemu.org | libvirt.org
next prev parent reply other threads:[~2019-02-28 18:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-27 16:20 [Qemu-devel] [PATCH v6 0/3] nbd: support for authorization control on TLS connections Daniel P. Berrangé
2019-02-27 16:20 ` [Qemu-devel] [PATCH v6 1/3] qemu-nbd: add support for authorization of TLS clients Daniel P. Berrangé
2019-02-27 16:43 ` Eric Blake
2019-02-27 16:50 ` Daniel P. Berrangé
2019-02-28 18:20 ` Eric Blake [this message]
2019-02-28 18:11 ` Eric Blake
2019-02-28 18:18 ` Daniel P. Berrangé
2019-02-28 18:27 ` Eric Blake
2019-02-27 16:20 ` [Qemu-devel] [PATCH v6 2/3] nbd: allow authorization with nbd-server-start QMP command Daniel P. Berrangé
2019-02-27 16:20 ` [Qemu-devel] [PATCH v6 3/3] nbd: fix outdated qapi docs syntax for tls-creds Daniel P. Berrangé
2019-02-27 16:44 ` Eric Blake
2019-02-28 18:41 ` [Qemu-devel] [PATCH v6 0/3] nbd: support for authorization control on TLS connections Eric Blake
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=75393117-5893-4ca1-f86b-83913a924e53@redhat.com \
--to=eblake@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=dgilbert@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@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).