| Summary: | vino makes unexpected network accesses | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Sullivan <jsrhbz> |
| Component: | vino | Assignee: | Søren Sandmann Pedersen <sandmann> |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 14 | CC: | kem, sandmann |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-08-16 15:45:33 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
(Just in case you think this is completely trivial: a random webservice with no obvious connection to Fedora or Gnome is getting told about every single publicly accessible passwordless VNC server in the world, with the endpoint address transmitted IN THE CLEAR.) This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping |
vino-2.32.2-1.fc14.x86_64 While playing around with the Remote Desktop Preferences dialog tracking down other issues, I noticed the network reachability message. Wondering how it worked I started digging into that. Turns out that it makes xmlrpc calls to URLs contained in /usr/share/vino/webservices which contains: # Jorge Pereira http://blog.jorgepereira.com.br/jorge/org.gnome.vino.Service.php # Jonh Wendell http://www.bani.com.br/vino/vino.php This was unexpected! Not I'm not *too* concerned about that, but some people are quite sensitive to their machines randomly "phoning home", especially when "home" isn't anywhere predictable or official. 1) Might it be better to replace these with (visibly) Fedora/Redhat hosted services? 2) Perhaps the preferences dialog should wait and ask for permission before doing this test. A "Check Connectivity" button would work. It should of course say *where* it will attempt to connect to before you click. 3) In general, how can you predict/enumerate/limit the external hosts a box will automatically connect to, before a user has even attempted to do anything that would plausibly trigger one? Obviously if I browse to www.google.com I expect a connection to go there. I sort of expect PackageKit connections to the repo, but can disable those. (It would have been nice to have been asked to enable automatic scans for updates first though.) Similarly for things like Firefox Addons updates, Adobe Reader/Java updates, CDDB lookups from media players. This one's a bit weirder though. Why would I have expected it to go *there*? I think there ought to be a Policy(TM) on this!