aboutsummaryrefslogtreecommitdiff
path: root/hmp.c
diff options
context:
space:
mode:
authorDaniel P. Berrange <berrange@redhat.com>2019-02-27 16:20:34 +0000
committerEric Blake <eblake@redhat.com>2019-03-06 11:05:27 -0600
commit000194556b65970a19ca437cd96b804a3f069f11 (patch)
tree3ca23aafe1f56a6e1345be4f2700a1f846a4bf71 /hmp.c
parentb25e12daff2c3e5ba933f85e8ba278f5bcba8f4d (diff)
downloadqemu-000194556b65970a19ca437cd96b804a3f069f11.zip
qemu-000194556b65970a19ca437cd96b804a3f069f11.tar.gz
qemu-000194556b65970a19ca437cd96b804a3f069f11.tar.bz2
nbd: allow authorization with nbd-server-start QMP command
As with the previous patch to qemu-nbd, the nbd-server-start QMP command also needs to be able to specify authorization when enabling TLS encryption. First the client must create a QAuthZ object instance using the 'object-add' command: { 'execute': 'object-add', 'arguments': { 'qom-type': 'authz-list', 'id': 'authz0', 'parameters': { 'policy': 'deny', 'rules': [ { 'match': '*CN=fred', 'policy': 'allow' } ] } } } They can then reference this in the new 'tls-authz' parameter when executing the 'nbd-server-start' command: { 'execute': 'nbd-server-start', 'arguments': { 'addr': { 'type': 'inet', 'host': '127.0.0.1', 'port': '9000' }, 'tls-creds': 'tls0', 'tls-authz': 'authz0' } } Reviewed-by: Eric Blake <eblake@redhat.com> Reviewed-by: Juan Quintela <quintela@redhat.com> Signed-off-by: Daniel P. Berrange <berrange@redhat.com> Message-Id: <20190227162035.18543-3-berrange@redhat.com> Signed-off-by: Eric Blake <eblake@redhat.com>
Diffstat (limited to 'hmp.c')
-rw-r--r--hmp.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/hmp.c b/hmp.c
index c2ad3f8..4a702d5 100644
--- a/hmp.c
+++ b/hmp.c
@@ -2373,7 +2373,7 @@ void hmp_nbd_server_start(Monitor *mon, const QDict *qdict)
goto exit;
}
- nbd_server_start(addr, NULL, &local_err);
+ nbd_server_start(addr, NULL, NULL, &local_err);
qapi_free_SocketAddress(addr);
if (local_err != NULL) {
goto exit;