As far as I know, the HTTP server is Vino is not used in Ubuntu. So as a workaround, the HTTP server can be disabled by passing the --disable- http-server flag during configuration.
** Patch added: "Patch for debian/rules to disable HTTP server" https://bugs.launchpad.net/ubuntu/+source/vino/+bug/984093/+attachment/4138370/+files/disable-http-server.patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to vino in Ubuntu. https://bugs.launchpad.net/bugs/984093 Title: vino http server binds to external interfaces despite local_only configuration Status in GNOME Remote Desktop: New Status in “vino” package in Ubuntu: Triaged Bug description: Environment: Debian Wheezy Vino 3.2.2-1+b1 Vino is configured for local access only via: gconftool-2 --set /desktop/gnome/remote_access/local_only --type bool true Vino's vnc server is only listening on localhost:5900 and no other interfaces - as expected. Vino's http server, though, is listening on all interfaces, despite the local_only configuration. The expected behaviour would be for all vino services, including the http server, to only bind to the localhost interface when configured accordingly. To manage notifications about this bug go to: https://bugs.launchpad.net/vino/+bug/984093/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
