From: "Daniel P. Berrange" <berrange@redhat.com>
To: Attila-Mihaly Balazs <dify.ltd@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Bind VNC to localhost unless otherwise specified to increase security
Date: Tue, 7 Jun 2016 10:28:57 +0100 [thread overview]
Message-ID: <20160607092857.GC20196@redhat.com> (raw)
In-Reply-To: <CAOqyLXiTL+gSwSo4rTF4ftJnwFbz7eHwuQe+F3RcMLGX_pfm3A@mail.gmail.com>
On Mon, Jun 06, 2016 at 06:39:15PM +0300, Attila-Mihaly Balazs wrote:
> Signed-off-by: Attila-Mihaly Balazs
> ---
> qemu-options.hx | 7 ++++++-
> ui/vnc.c | 2 ++
> 2 files changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/qemu-options.hx b/qemu-options.hx
> index 9f33361..80ade0d 100644
> --- a/qemu-options.hx
> +++ b/qemu-options.hx
> @@ -1245,7 +1245,12 @@ syntax for the @var{display} is
>
> TCP connections will only be allowed from @var{host} on display @var{d}.
> By convention the TCP port is 5900+@var{d}. Optionally, @var{host} can
> -be omitted in which case the server will accept connections from any host.
> +be omitted in which case the server will only accept connections from
> +localhost. To accept connections on a given network interface use the
> +syntax @var{interface IP}:@var{d} (for example @var{192.168.1.2}:@var{1}
> +or @var{[::1]}:@var{1}). To listen on all network interfaces specify
> +@var{0.0.0.0}:@var{d}. Warning! Please make sure that you have authentication
> +set up before exposing VNC to the internet!
>
> @item unix:@var{path}
>
> diff --git a/ui/vnc.c b/ui/vnc.c
> index c862fdc..b4597e4 100644
> --- a/ui/vnc.c
> +++ b/ui/vnc.c
> @@ -3576,6 +3576,8 @@ void vnc_display_open(const char *id, Error **errp)
> inet = saddr->u.inet.data = g_new0(InetSocketAddress, 1);
> if (vnc[0] == '[' && vnc[hlen - 1] == ']') {
> inet->host = g_strndup(vnc + 1, hlen - 2);
> + } else if (hlen == 0) {
> + inet->host = g_strdup("localhost");
I understand the reason you want to do this change, but I don't really
like the fact that this is making "empty hostname" semantics for the -vnc
option, diverge from the "empty hostname" semantics for other QEMU args
like -chardev. The main point of having all of QEMU use the same code
for sockets listen/connect setup via the InetSocketAddress struct is that
we gain consistent semantics across the whole codebase. This change to
VNC code is throwing away that consistency, so I'm against this change
really.
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 :|
next prev parent reply other threads:[~2016-06-07 9:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-06 15:39 [Qemu-devel] [PATCH] Bind VNC to localhost unless otherwise specified to increase security Attila-Mihaly Balazs
2016-06-06 15:49 ` Attila-Mihaly Balazs
2016-06-07 9:28 ` Daniel P. Berrange [this message]
[not found] ` <CAOqyLXhvW8QoVhG1ARPaa729hax_hqUu+ykqDQHA3=mtqNbrMQ@mail.gmail.com>
[not found] ` <1465332173.14901.158.camel@redhat.com>
2016-06-21 17:33 ` Attila-Mihaly Balazs
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=20160607092857.GC20196@redhat.com \
--to=berrange@redhat.com \
--cc=dify.ltd@gmail.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).