A bit off topic for this list but I hope you're adding the ability to configure a network as a friendly/trusted network vs a hostile network. Similar to what Windows has when you connect it to a new network. If you let it know that you're on a friendly network there should be some way to enable all these services to auto-advertise themselves. Otherwise they will becoming an annoying mess of having to enable every service in every way to advertise itself.

Actually, it is possible to remotely connect to any libvirtd instance using an SSH tunnel, which works out of the box. Only the direct, non-tunnelled TLS/SASL based connections require manual setup.

> I hope that makes sense. Let me know if I've gotten something wrong. > > Would you accept a patch to do this? Or would you suggest that we > try and do this downstream in the Fedora/RHEL packages instead? Our policy for Fedora / RHEL is to not change upstream behaviour, so this kind of policy decision should be resolved here.

While apps like virt-manager do have the ability to use mDNS to locate remote libvirtd servers, my gut feeling is that it is probably rarely used. So given the need to tradeoff off out of the box usability against privacy concerns, I think we could probably say turning off mDNS by default is acceptable. What do others think ?

>From ef831d7c35871f26964742ca1de49ef464dd7bbb Mon Sep 17 00:00:00 2001 From: Stef Walter <stefw(a)gnome.org&gt; Date: Tue, 27 Mar 2012 13:59:07 +0200 Subject: [PATCH] Change the default of mdns_adv to false * Don't advertise information on the network without consent of the user, either through manual configuration, or a user interface that drives this option. * Since libvirtd must be configured for network access anyway this setting was not useful "out of the box", so changing this default setting does not remove "out of the box" functionality.

--- daemon/libvirtd.c | 2 +- daemon/libvirtd.conf | 4 ++-- daemon/test_libvirtd.aug | 8 ++++---- docs/remote.html.in | 2 +- tests/confdata/libvirtd.conf | 4 ++-- tests/confdata/libvirtd.out | 4 ++-- 6 files changed, 12 insertions(+), 12 deletions(-)

On Mon, Mar 26, 2012 at 09:31:44PM +0200, Stef Walter wrote: > In the GNOME UI we'd like to make use of Avahi discovery and name > resolution "out of the box". A typical use case is for discovery of > printers that are advertised using MDNS. This should work even on > potentially 'hostile' networks such as a wireless access point in a > print shop or airport. It should work without user configuration. > > https://fedoraproject.org/wiki/Desktop/Whiteboards/AvahiDefault > > In order to turn on Avahi by default, and make it work by default, > we'd like to make it possible to use Avahi without advertising any > information to the network by default. Advertising information to > the network (even the host name) without the user's configuration or > consent is a privacy issue. > > libvirtd advertises itself via MDNS on the network by default. I > understand that MDNS discovery of libvirtd is really handy in many > cases. > > However since one has to configure network access in libvirtd anyway > -- none of the access methods work "out of the box" to my > understanding -- I'd like to suggest turning off libvirtd's MDNS > publishing by default. As part of setting up libvirtd for network > access, the user would turn on mdns_adv. Actually, it is possible to remotely connect to any libvirtd instance using an SSH tunnel, which works out of the box. Only the direct, non-tunnelled TLS/SASL based connections require manual setup. But since, IIUC, the default Fedora firewall setup blocks mDNS, it still wouldn't work out of the box. > I hope that makes sense. Let me know if I've gotten something wrong. > > Would you accept a patch to do this? Or would you suggest that we > try and do this downstream in the Fedora/RHEL packages instead? Our policy for Fedora / RHEL is to not change upstream behaviour, so this kind of policy decision should be resolved here. While apps like virt-manager do have the ability to use mDNS to locate remote libvirtd servers, my gut feeling is that it is probably rarely used. So given the need to tradeoff off out of the box usability against privacy concerns, I think we could probably say turning off mDNS by default is acceptable. What do others think ?

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 :| -- libvir-list mailing list libvir-list(a)redhat.com https://www.redhat.com/mailman/listinfo/libvir-list