From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: "Daniel P. Berrange" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, lcapitulino@redhat.com,
marcandre.lureau@redhat.com, armbru@redhat.com
Subject: Re: [Qemu-devel] [PATCH] hmp: Update info vnc
Date: Wed, 5 Jul 2017 17:33:24 +0100 [thread overview]
Message-ID: <20170705163324.GC2284@work-vm> (raw)
In-Reply-To: <20170705162811.GI22008@redhat.com>
* Daniel P. Berrange (berrange@redhat.com) wrote:
> On Wed, Jul 05, 2017 at 03:43:02PM +0100, Dr. David Alan Gilbert (git) wrote:
> > From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
> >
> > The QMP query-vnc interfaces have gained a lot more information that
> > the HMP interfaces hasn't got yet. Update it.
> >
> > Note the output format has changed, but this is HMP so that's OK.
> >
> > In particular, this now includes client information for reverse
> > connections:
> >
> > -vnc :0
> > (qemu) info vnc
> > default:
> > Server: 0.0.0.0:5900 (ipv4)
> > Auth: none (Sub: none)
> > Auth: none (Sub: none)
>
> If you're reporting Auth: against the individual Server entry,
> there's no reason to report it at the top level too. We only
> keep that duplication in QMP for sake of backcompat, which
> is not important for HMP
Where would it get reported for a 'reverse' connection then?
That has no server entry.
Dave
> >
> > (Now connect a client)
> >
> > (qemu) info vnc
> > default:
> > Server: 0.0.0.0:5900 (ipv4)
> > Auth: none (Sub: none)
> > Client: 127.0.0.1:51828 (ipv4)
> > x509_dname: none
> > username: none
> > Auth: none (Sub: none)
> >
> > -vnc localhost:7000,reverse
> > (qemu) info vnc
> > default:
> > Client: ::1:7000 (ipv6)
> > x509_dname: none
> > username: none
> > Auth: none (Sub: none)
> >
> > -vnc :1,password,id=rev -vnc localhost:7000,reverse
> > (qemu) info vnc
> > default:
> > Client: ::1:7000 (ipv6)
> > x509_dname: none
> > username: none
> > Auth: none (Sub: none)
> > rev:
> > Server: 0.0.0.0:5901 (ipv4)
> > Auth: vnc (Sub: none)
> > Client: 127.0.0.1:53616 (ipv4)
> > x509_dname: none
> > username: none
> > Auth: vnc (Sub: none)
> >
> > This was originally RH bz 1461682
> >
> > Signed-off-by: Dr. David Alan Gilbert <dgilbert@redhat.com>
>
> 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 :|
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2017-07-05 16:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 14:43 [Qemu-devel] [PATCH] hmp: Update info vnc Dr. David Alan Gilbert (git)
2017-07-05 16:21 ` Marc-André Lureau
2017-07-06 9:41 ` Dr. David Alan Gilbert
2017-07-05 16:28 ` Daniel P. Berrange
2017-07-05 16:33 ` Dr. David Alan Gilbert [this message]
2017-07-06 8:02 ` Daniel P. Berrange
2017-07-06 9:52 ` Dr. David Alan Gilbert
2017-07-07 14:44 ` Markus Armbruster
2017-07-11 14:35 ` Dr. David Alan Gilbert
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=20170705163324.GC2284@work-vm \
--to=dgilbert@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=lcapitulino@redhat.com \
--cc=marcandre.lureau@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).