| Author | Message | ||
     Methhanithodugu Hero Username: Methhanithodugu Post Number: 16624 Registered: 12-2008 Posted From: 117.195.201.133 Rating: N/A |
hellow Emaina mathi undaa aa article eppudu aithe emiti problem e roju naaku vachindi ... googleupdater.exe gurinchi google seyyakunda nee experience ettu is its safe or is it eavesdropping BTW i dont use google + or google chat /talk FYI  Golden Spoon | ||
| Adj Junior Artist Username: Adj Post Number: 172 Registered: 09-2011 Posted From: 173.70.108.135 Rating: N/A |
Welcome to 2012. Article dated February 13, 2009 | 10:42 am | ||
| Methhanithodugu Hero Username: Methhanithodugu Post Number: 16618 Registered: 12-2008 Posted From: 117.195.201.133 Rating: N/A |
Here are a few reasons why an always-active daemon (software speak for a tiny app that runs in the background) for handling software updates is a bad idea: It opens up an always-on tunnel to Google. While Google may be confident its update servers will never be compromised, how confident are you? If a third party gains control of that server, it can inject nearly any code it wants into your machine. It’s always on, always looking for update. On an expensive, pay-by-the-megabyte EVDO network? Google Updater doesn’t care and will suck down any available updates without asking, costing you money. Google updates Google Earth or Picasa or Gtalk, but the update ends up having a bug that wipes data from your drive. Sorry, too late — the auto-updater already grabbed the latest version without asking. Kiss your data goodbye. Administering a large network that needs to be locked down and tightly controlled? Cross Google software off your list. All the above problems apply, but they’re cascaded across your network for added headaches. Read Complete here http://www.wired.com/epicenter/2009/02/why-googles-sof/  Golden Spoon |
