qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange@redhat.com>
To: Gonglei <arei.gonglei@huawei.com>
Cc: qemu-devel@nongnu.org, Gerd Hoffmann <kraxel@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] ui: fix regression in x509verify parameter for VNC server
Date: Wed, 11 Mar 2015 09:45:29 +0000	[thread overview]
Message-ID: <20150311094529.GB22609@redhat.com> (raw)
In-Reply-To: <54FF9EFE.8000706@huawei.com>

On Wed, Mar 11, 2015 at 09:48:46AM +0800, Gonglei wrote:
> On 2015/3/11 0:27, Daniel P. Berrange wrote:
> > The 'x509verify' parameter is documented as taking a path to the
> > x509 certificates, ie the same syntax as the 'x509' parameter.
> > 
> >   commit 4db14629c38611061fc19ec6927405923de84f08
> >   Author: Gerd Hoffmann <kraxel@redhat.com>
> >   Date:   Tue Sep 16 12:33:03 2014 +0200
> > 
> >     vnc: switch to QemuOpts, allow multiple servers
> > 
> > caused a regression by turning 'x509verify' into a boolean
> > parameter instead. This breaks setup from libvirt and is not
> > consistent with the docs.
> > 
> > Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
> > ---
> >  ui/vnc.c | 9 +++++++--
> >  1 file changed, 7 insertions(+), 2 deletions(-)
> > 
> > diff --git a/ui/vnc.c b/ui/vnc.c
> > index 10a2724..37290e7 100644
> > --- a/ui/vnc.c
> > +++ b/ui/vnc.c
> > @@ -3304,7 +3304,7 @@ static QemuOptsList qemu_vnc_opts = {
> >              .type = QEMU_OPT_BOOL,
> >          },{
> >              .name = "x509verify",
> > -            .type = QEMU_OPT_BOOL,
> > +            .type = QEMU_OPT_STRING,
> >          },{
> >              .name = "acl",
> >              .type = QEMU_OPT_BOOL,
> > @@ -3391,9 +3391,14 @@ void vnc_display_open(const char *id, Error **errp)
> >  #ifdef CONFIG_VNC_TLS
> >      tls  = qemu_opt_get_bool(opts, "tls", false);
> >      path = qemu_opt_get(opts, "x509");
> > +    if (!path) {
> > +        path = qemu_opt_get(opts, "x509verify");
> > +        if (path) {
> > +            vs->tls.x509verify = true;
> > +        }
> > +    }
> >      if (path) {
> >          x509 = true;
> > -        vs->tls.x509verify = qemu_opt_get_bool(opts, "x509verify", false);
> 
> We still need to get the x509verify value, while both 'x509' and 'x509verify'
> are configured, isn't it?

Err, the code 7 lines earlier gets the x509verify value. The x509 and x509verify
parameters are never to be specified at the same time - either one or the other
is used.


Regards,
Daniel
-- 
|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

  reply	other threads:[~2015-03-11  9:45 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 16:27 [Qemu-devel] [PATCH] ui: fix regression in x509verify parameter for VNC server Daniel P. Berrange
2015-03-11  1:48 ` Gonglei
2015-03-11  9:45   ` Daniel P. Berrange [this message]
2015-03-11 11:07     ` Gonglei
2015-03-11 11:10       ` Daniel P. Berrange
2015-03-11 11:24         ` Gonglei
2015-03-11 11:27           ` Daniel P. Berrange
2015-03-11 11:30             ` Gonglei
2015-03-11 13:25 ` Gerd Hoffmann

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=20150311094529.GB22609@redhat.com \
    --to=berrange@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=kraxel@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).