News for hackers. Stuff that matters.
Re:Google Chrome Keystone is modifying /var symlink on non S... by cbsmith on Tuesday September 24, 2019 @10:09PM (#21066878)
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.
Re:Google Chrome Keystone is modifying /var symlink on non S... by apostacy on Wednesday September 25, 2019 @12:07AM (#21067507)
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.

Re:Google Chrome Keystone is modifying /var symlink on non S... by kevingadd on Wednesday September 25, 2019 @04:50AM (#21068942)
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.
Re:Google Chrome Keystone is modifying /var symlink on non S... by Already__Taken on Wednesday September 25, 2019 @07:17AM (#21069604)
at-launch check would obviously delay launch. Users do not want chrome to start slower I thought this would be obvious.