On 5 January 2015 at 18:13, Daniel P. Berrange wrote:
> Configuring 0.0.0.0 and no auth is a valid setup *provided* the virtualization
> host itself is on a secured network. In fact this is the normal setup for an
> OpenStack deployment, since the virt host/VNC server is not intended to ever
> be
On Mon, Dec 29, 2014 at 09:26:45PM +, Peter Maydell wrote:
> On 29 December 2014 at 19:09, Attila-Mihaly Balazs wrote:
> > My suggestion for improvement would be:
> > - change the behaviour of "-vnc :port" such that it listens on "127.0.0.1"
> > when the IP isn't specified
> > - if host is "0.
On 29 December 2014 at 19:09, Attila-Mihaly Balazs wrote:
> My suggestion for improvement would be:
> - change the behaviour of "-vnc :port" such that it listens on "127.0.0.1"
> when the IP isn't specified
> - if host is "0.0.0.0" (perhaps also include any routable IPv4 addresses -
> and non-link
Dear all,
Some enterprising people scanned the whole range of IPv4 addresses for open
VNC servers [1] and my casual browsing seems to indicate that a lot of them
are QEMU VMs. I suspect that this is because just doing "-vnc :1" will
listen on/bind to "0.0.0.0" (ie. on all the interfaces).
My sugg
