After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 335229 - improve server configuration
improve server configuration
Status: RESOLVED DUPLICATE of bug 156242
Product: vino
Classification: Applications
Component: Server
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: Vino Maintainer(s)
Vino Maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2006-03-20 14:37 UTC by Benoît Dejean
Modified: 2006-10-23 10:43 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Benoît Dejean 2006-03-20 14:37:56 UTC 
Hi it would be nice to be able to configure :
- on which interfaces vino has to listen
- some kind of ACL

By the way, default configuration (listen on *, no password) is very dangerous.

Thanks.
Comment 1 Mark McLoughlin 2006-10-23 10:43:22 UTC 
For the first one, we now have the local_only preference

For the second, it falls under the general "VNC authentication sucks" category which is well-known and documented in e.g. docs/remote-desktop.txt. I don't think there's too much point in tracking it in bugzilla unless we've a more detailed analysis of the options available to us (and perhaps a patch :-)

And note that the default configuration is actually "listen on *, no password, prompt the user" ... i.e. there is manual authentication

Marking as a dup of bug #156242, but I do agree that we could do with some more detailed research on other authentication mechanisms we could provide

*** This bug has been marked as a duplicate of 156242 ***