News for hackers. Stuff that matters.
Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate by kodablah on Monday November 14, 2016 @07:51PM (#12954744)
I fail to see this as any more harmful than the auto updating feature. I understand the concern of multiple avenues to phone home as being worse than one, but it's negligible considering it's the same company. Coupled with all of their other services for security incidents, prediction, auto correct, spelling, usage stats, dangerous page warnings, etc, I think it's just another log on the fire and not worth being concerned about specifically.
Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate by Ph0X on Monday November 14, 2016 @09:37PM (#12955180)
It actually is almost nothing like the auto updating feature.

Finch is mainly used for A/B testing. It doesn't push actual updates, all it does it turn existing features (flags) on and off. It's used for quickly A/B testing or incremental rolling new features and is designed to be more agile.

Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate by wfunction on Tuesday November 15, 2016 @02:33AM (#12956299)
That means it uniquely identified you to Google every day then, right?
Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate by gcb0 on Tuesday November 15, 2016 @06:01AM (#12957087)
> using a Google browser

> not wanting to be tracked

here's a hint: ad impression for unknown user is 0.01$ and for logged in user 2$. guess why Google has a browser now...

Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate by wfunction on Friday November 18, 2016 @04:48AM (#12985566)
Do you mean logged into Chrome (e.g. profile sync)? or just logged into Gmail?
Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate by gcb0 on Sunday November 20, 2016 @08:13PM (#13002353)
does not matter at all.

if you have a logged-off cookie, and the publisher can associate you with a logged-in user at a near point in time, they can charge you as logged in impression.

Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate by phreack on Tuesday November 15, 2016 @03:10AM (#12956408)
Always assume so with Google products.
Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate by wfunction on Tuesday November 15, 2016 @05:01AM (#12956859)
What about Chromium?
Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate by vurpo on Tuesday November 15, 2016 @05:36AM (#12956984)
Chromium never uses Finch except if you specify it in the command line flags.
Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate by wfunction on Tuesday November 15, 2016 @06:11AM (#12957130)
Thanks!
Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate by gsnedders on Tuesday November 15, 2016 @09:30AM (#12958227)
Does it? Does the request actually provide enough to uniquely identify you?
Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate by yuhong on Wednesday November 16, 2016 @06:56PM (#12972830)
Re:Why Chrome 53 Is Rejecting Chase Bank's Symantec Certificate by xg15 on Tuesday November 15, 2016 @08:28AM (#12957759)
The biggest difference I see is the speed. You're right, it doesn't make a difference from a technical point of view but it illustrates again just how much power they have over chrome - and thereby over the web: They can push a policy update to the bigger part of Chrome's userbase in 24 hours.

It should be entertaining when car makers use the same strategy: "Oh yeah, we have this system where everytime you turn the ignition, your car polls us and updates its assistant, motor, steering and airbag settings. Don't worry though, we mostly just use it for randomized tests and field trials."