I don't disagree w/ the fact that there's a use case for listening on INADDR_ANY, I'm saying that it is a security hole and a security hole that's easily fixable w/ a single gui option that can determine if it should bind to 127.0.0.1 or INADDR_ANY and a few lines of code to handle that option.
** Bug watch added: GNOME Bug Tracker #156242 http://bugzilla.gnome.org/show_bug.cgi?id=156242 ** Also affects: vino (upstream) via http://bugzilla.gnome.org/show_bug.cgi?id=156242 Importance: Unknown Status: Unknown -- vino listen on all addresses https://launchpad.net/bugs/54312 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
