Currently Being ModeratedAug 9, 2012 1:37 AM (in response to RandypTulsa)
Maybe it was the order I did it in:
- Change "Everyone" Priviledge to "No Access" by highlighting it and using the tool dropdown
- Unlock lower right lock icon
- Lock folder in "Preview" by just clicking on it
- Lock the lower right icon last
I think that's right, or maybe 1 and 2 are reversed. Hope that helps!
Currently Being ModeratedAug 14, 2012 8:39 AM (in response to RandypTulsa)
I was just following this thread and thought the same thing. If you go to the general section in the Get info window there are two checkboxes at the bottom. Tick the 'locked' one and the lock icon appears by the Folder. Don't know if this makes any difference to the solution but doesn't seem to hurt.
Currently Being ModeratedAug 18, 2012 7:05 AM (in response to darknight00z)
I had no that idea that had been published. Possibly. I was in Lion, and I could only find the google folder in one of the libraries, never the other one. Of course, you have to have or have had google software installed for it to be there.
Currently Being ModeratedAug 19, 2012 7:26 AM (in response to darknight00z)
Well I was confronted to more or less the same problem as you. I finally was able to get rid of it through the following procedure:
defaults write com.google.Keystone.Agent checkInterval 0
Hope this helps.
Currently Being ModeratedAug 22, 2012 12:05 PM (in response to Rodko)
Thanks everyone for this thread - I followed the instructions and it seems to have gotten rid of the problem. One question though - after disabling the ksfetch (or rather eliminating the privelleges in the library folder) does this mean I will no longer be able to auto update the chrome brower? How do I know if chrome is still updating itself regularly and the extenstions I have added to it?
Currently Being ModeratedAug 30, 2012 9:43 PM (in response to Rodko)
Currently Being ModeratedOct 2, 2012 11:40 AM (in response to JoergSi)
Yeah the trick that Google is using is that their software is making a copy of the ksfetch process inside a tmp folder each time it executes. Little Snitch sees that as a unique process assigned a unique rule every time it runs.
The Hands Off solution using the *asterisks* solves it because it applies the rule to any instance of ksfetch regardless of location. I wonder if Little Snitch supports it too?
I tried the chmod 000 solution for now.
Currently Being ModeratedOct 20, 2012 11:13 PM (in response to Rodko)
I used the terminal method to restrict the update requests to once every 30 days. After a month it started coming back several times per hour. While searching for a solution to stop it again I came across this post in another forum:
Hi folks, if you're using the
defaults write com.google.Keystone.Agent checkInterval 2500000
method (simply entered into terminal, which delays the check to only once every 2,500,000 seconds, which is once a month -- or change to "0" for never, although if Google ever deigns to fix this, you'll want the update), then keep in mind that you STILL have to "satisfy" the LAST call or it will keep screaming every few minutes! This "defaults" method in IMHO is the best "solution". So let the one call through your filter or firewall to check and finish its update, then this effing virus will shut the poop up for two and a half million seconds -- one month -- until the next check... of course executed sneakily from some new temporary directory. Each month (or whatever you set the interval to) you need to say "yes" to it: to click it through your application filter or firewall just once (well, actually, twice in rapid succession) in order for this to work.
It's a heck of a lot better than every two minutes. And this is the only workaround apparently that the cocky Google royalty "supports", reluctantly, to "opt-out" of what they pretend is in all of our "best interests". (Imagine any other third-party software behaving this way!) I choose the "approved" method instead of deleting or locking files and folders or whatever, to avoid any unintended consequences down the road of mucking with system files, installs or permission changes (which may not stick after updates or routine system tasks.)
Currently Being ModeratedNov 3, 2012 4:38 PM (in response to iHatePC)
I've read a lot of solutions, now, to this problem, including the suggestion to install a special "get rid of this problem" app (http://wireload.net/products/guu-google-update-uninstaller/).
But I think that iHatePC is by far the best solution: have it update only once a month. That solves both the problem of too many intrusions, and the problem of "whoa, but I want to be updated, I don't want buggy or insecure versions of Chrome running too long".