[Desktop-packages] [Bug 984093] Re: vino http server binds to external interfaces despite local_only configuration
** Changed in: vino (Ubuntu) Status: Triaged => Fix Committed -- 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 vino: Fix Released Status in vino package in Ubuntu: Fix Committed 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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 984093] Re: vino http server binds to external interfaces despite local_only configuration
This bug was fixed in the package vino - 3.8.1-0ubuntu7 --- vino (3.8.1-0ubuntu7) xenial; urgency=medium * debian/patches/git_struct_init.patch: - "Be more careful with memory allocation", should fix some of the segfault issues reports (lp: #987287) * debian/patches/git_small_bugfixes.patch: - backport some easy bugfixes * debian/patches/git_no_http_server.patch: - remove http server, it's not used and listen on interfaces for no reason (lp: #984093) -- Sebastien BacherFri, 20 Nov 2015 16:51:19 +0100 ** Changed in: vino (Ubuntu) Status: Fix Committed => Fix Released -- 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 vino: Fix Released Status in vino package in Ubuntu: Fix Released 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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 984093] Re: vino http server binds to external interfaces despite local_only configuration
Current situation on 14.04 LTS is the port 5800 is still open and currently responds to HTTP requests with: htmlheadtitleFile Not Found/title/head bodyh1File Not Found/h1/body/html Verified this was vino by killing it to see the port closed. Verified on a remote machine. In my testing I used the instructions in https://help.ubuntu.com/community/VNC/Servers were followed to allow only local connections. -- 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: Fix Released 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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 984093] Re: vino http server binds to external interfaces despite local_only configuration
** Changed in: vino Status: New = Fix Released -- 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: Fix Released 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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 984093] Re: vino http server binds to external interfaces despite local_only configuration
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 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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 984093] Re: vino http server binds to external interfaces despite local_only configuration
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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 984093] Re: vino http server binds to external interfaces despite local_only configuration
The attachment Patch for debian/rules to disable HTTP server seems to be a patch. If it isn't, please remove the patch flag from the attachment, remove the patch tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: 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 : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp