Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm not even quite sure why Google does it. Can't they just check and fetch updates while Chrome is open? What's it matter if Chrome is out of date if it isn't running? Are they trying to push off updates to the middle of the night or something? That doesn't really make sense, since people probably mostly leave their browser open anyways.

I had Chrome installed "just in case" (mainly for the dev tools for the rare occasion I do web dev) and I just uninstalled it and the updater. It's not worth the surface area...

Now to get around to nuke all this junk that Citrix Receiver installs. Ugh.



It's a better way to mitigate against zero days in the browser, where you might get exploited even before you find out the browser is out of date.


While that is true, I do not believe that is why they are doing it that way. There's nothing stopping them from giving some minimal feedback that an update happened. It would actually be better that they did.

It is also suspicious how set they are so against users using an older version of their browser. Security is not a good enough justification. It is actually easier to use an older Operating System than an older version of Chrome.

This is clearly just to protect the integrity of their platform.


What kind of zero-day does this protect against that wouldn't be blocked by an at-launch-time update check like most regular software uses? If anything, at-launch-time is better because Keystone's last update check might have been 2 hours before the 0day patch came out, but at-launch-time would check immediately and notice.


at-launch check would obviously delay launch. Users do not want chrome to start slower I thought this would be obvious.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: