From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Zihao Chang <changzihao1@huawei.com>
Cc: oscar.zhangbo@huawei.com, kraxel@redhat.com,
qemu-devel@nongnu.org, xiexiangyou@huawei.com, armbru@redhat.com
Subject: Re: [PATCH] vnc: add qmp to support reload vnc tls certificates
Date: Mon, 4 Jan 2021 12:27:40 +0000 [thread overview]
Message-ID: <20210104122740.GI640208@redhat.com> (raw)
In-Reply-To: <20210104071128.754-1-changzihao1@huawei.com>
On Mon, Jan 04, 2021 at 03:11:28PM +0800, Zihao Chang wrote:
> QEMU loads vnc tls certificates only when vm is started. This patch
> provides a new qmp command to reload vnc tls certificates without
> restart vnc-server/VM.
>
> Signed-off-by: Zihao Chang <changzihao1@huawei.com>
> ---
> include/ui/console.h | 1 +
> monitor/qmp-cmds.c | 7 +++++++
> qapi/ui.json | 17 +++++++++++++++++
> ui/vnc.c | 20 ++++++++++++++++++++
> 4 files changed, 45 insertions(+)
>
> diff --git a/include/ui/console.h b/include/ui/console.h
> index 5dd21976a3..f05140b662 100644
> --- a/include/ui/console.h
> +++ b/include/ui/console.h
> @@ -441,6 +441,7 @@ int vnc_display_password(const char *id, const char *password);
> int vnc_display_pw_expire(const char *id, time_t expires);
> QemuOpts *vnc_parse(const char *str, Error **errp);
> int vnc_init_func(void *opaque, QemuOpts *opts, Error **errp);
> +int vnc_display_reload_cert(const char *id, Error **errp);
>
> /* input.c */
> int index_from_key(const char *key, size_t key_length);
> diff --git a/monitor/qmp-cmds.c b/monitor/qmp-cmds.c
> index 34f7e75b7b..90bd08c8ed 100644
> --- a/monitor/qmp-cmds.c
> +++ b/monitor/qmp-cmds.c
> @@ -287,6 +287,13 @@ static void qmp_change_vnc(const char *target, bool has_arg, const char *arg,
> qmp_change_vnc_listen(target, errp);
> }
> }
> +
> +void qmp_reload_vnc_cert(Error **errp)
> +{
> + if (vnc_display_reload_cert(NULL, errp) < 0) {
> + error_setg(errp, "Reload vnc tls cert failed");
This error message is entirely useless at helping diagnose what
failed. We need to propagate real error messages from the root
cause.
> + }
> +}
> #endif /* !CONFIG_VNC */
>
> void qmp_change(const char *device, const char *target,
> diff --git a/qapi/ui.json b/qapi/ui.json
> index d08d72b439..bc3ffdb20f 100644
> --- a/qapi/ui.json
> +++ b/qapi/ui.json
> @@ -1179,3 +1179,20 @@
> ##
> { 'command': 'query-display-options',
> 'returns': 'DisplayOptions' }
> +
> +##
> +# @reload-vnc-cert:
> +#
> +# Reload certificates for vnc.
> +#
> +# Returns: nothing
> +#
> +# Since: 5.2
> +#
> +# Example:
> +#
> +# -> { "execute": "reload-vnc-cert" }
> +# <- { "return": {} }
> +#
> +##
> +{ 'command': 'reload-vnc-cert' }
> diff --git a/ui/vnc.c b/ui/vnc.c
> index 7452ac7df2..b0cfbcf47c 100644
> --- a/ui/vnc.c
> +++ b/ui/vnc.c
> @@ -582,6 +582,26 @@ VncInfo2List *qmp_query_vnc_servers(Error **errp)
> return prev;
> }
>
> +int vnc_display_reload_cert(const char *id, Error **errp)
> +{
> + VncDisplay *vd = vnc_display_find(id);
> +
> + if (!vd) {
> + return -EINVAL;
> + }
> +
> + if (!vd->tlscreds) {
> + error_printf_unless_qmp("If you want use vnc tls please enable "
> + "vnc tls using '-vnc tls-creds=${tls-obj-id}'.\n");
> + return -EPERM;
You're passing in a 'Error' object, so use that and don't retyrn errnos
> + }
> +
> + object_property_set_bool(OBJECT(vd->tlscreds), "loaded", false, NULL);
> + object_property_set_bool(OBJECT(vd->tlscreds), "loaded", true, NULL);
This is ignoring all errors which is not at all acceptable. It means on
failure to load the new certs, we're left with a broken creds object
which callers will not expect.
We need to be able to do this in a safe way such that we carry on using
the original TLS certs if loading the new ones fails. This can't be done
using the 'loaded' property- we need an explicit API to reload things.
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-01-04 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 7:11 [PATCH] vnc: add qmp to support reload vnc tls certificates Zihao Chang
2021-01-04 12:27 ` Daniel P. Berrangé [this message]
2021-01-15 13:25 ` Markus Armbruster
2021-01-19 19:23 ` 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=20210104122740.GI640208@redhat.com \
--to=berrange@redhat.com \
--cc=armbru@redhat.com \
--cc=changzihao1@huawei.com \
--cc=kraxel@redhat.com \
--cc=oscar.zhangbo@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=xiexiangyou@huawei.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.