[Bug 984093] Re: vino http server binds to external interfaces despite local_only configuration

[Jamie Strandboge]

Thanks for the patch! I'm uncomfortable ACKing this patch without more
supporting information that it disabling it won't break people. I think
the proper thing to do is continue to wait on upstream's response. It
would probably make the process go quicker if a patch was submitted
upstream that fixed the buggy behavior.

Unsubscribing ubuntu-sponsors for now. If you'd like to have a patch
applied to Ubuntu, please link to a bzr branch or supply a debdiff (see
https://wiki.ubuntu.com/SponsorshipProcess for details).

Thanks again.

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
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