News for hackers. Stuff that matters.
Re:Get Ready for New SameSite=None; Secure Cookie Settings by Animats on Wednesday October 23, 2019 @01:47PM (#21337017)
Why doesn't this break Google tracking?
Re:Get Ready for New SameSite=None; Secure Cookie Settings by syncerr on Wednesday October 23, 2019 @02:47PM (#21337581)
1/ Google Analytics uses 1st-party cookies since their scripts execute directly on websites. 2/ Chrome relays its own browsing data.
Re:Get Ready for New SameSite=None; Secure Cookie Settings by lrem on Wednesday October 23, 2019 @05:42PM (#21339336)
Can you point me at a link for 2?

Disclaimer: despite working for Google, I don't have a clue about this. I'm deep in the backend.

Re:Get Ready for New SameSite=None; Secure Cookie Settings by blacksmith_tb on Wednesday October 23, 2019 @07:14PM (#21340061)
Ostensibly for SafeBrowsing[1] I believe...

1: https://superuser.com/questions/75841/what-is-1e100-net-and-...

Re:Get Ready for New SameSite=None; Secure Cookie Settings by oldmanhorton on Wednesday October 23, 2019 @10:11PM (#21341043)
Well to start, there's browser history sync through your Google account. I'm not aware what the privacy policy is on that data, but I'd imagine it allows Google to get aggregate views at least at the domain level, if not the page level.
Re:Get Ready for New SameSite=None; Secure Cookie Settings by baroffoos on Wednesday October 23, 2019 @10:24PM (#21341122)
Also the fact that signing in to any google website automatically signs you in to the browser now.
Re:Get Ready for New SameSite=None; Secure Cookie Settings by lrem on Sunday October 27, 2019 @07:12AM (#21369032)
Re:Get Ready for New SameSite=None; Secure Cookie Settings by y42 on Thursday October 24, 2019 @03:07AM (#21342351)
GA usually comes from a Google-domain. Implementing GA on one of your properties always means using 3rd-party cookies (as long as you not configure some CNAME-records to point your own 1st party tracking domain to GA's tracking domain). Where the script is being executed does not matter in this case, the script is just building the tracking request to the tracking app.
Re:Get Ready for New SameSite=None; Secure Cookie Settings by hirsin on Wednesday October 23, 2019 @01:50PM (#21337047)
They (will) add the samesite decorators.
Re:Get Ready for New SameSite=None; Secure Cookie Settings by yoloClin on Wednesday October 23, 2019 @07:54PM (#21340279)
The intent isn't to break tracking, it's to prevent CSRF.

One of the nice side effects is it will temporarily break tracking, though.