News for hackers. Stuff that matters.
Re:Get Ready for New SameSite=None; Secure Cookie Settings by jimbo1qaz on Thursday October 24, 2019 @02:59AM (#21342324)
I've heard that https://tools.ietf.org/html/rfc2109 (the cookie RFC) was originally meant to not allow third-party cookies by default.

In my opinion, cookies on cross-site requests (third-party cookies) should be sent to web servers under a different request header, since they're semantically different (do not necessarily imply user authorization and intent) from cookies attached to a request initiated by the user from a first-party page.

Re:Get Ready for New SameSite=None; Secure Cookie Settings by Thorrez on Thursday October 24, 2019 @03:26AM (#21342445)
>cross-site requests (third-party cookies)

I thought "third-party cookies" generally referred to cookies that were set in a third-party context. Whereas you're talking about cookies being read in a third-party context.

Re:Get Ready for New SameSite=None; Secure Cookie Settings by RaiseProfits on Thursday October 24, 2019 @12:14PM (#21346073)
What is a scenario that would illustrate the difference? On paper third party cookie just means “any cookie from another domain”. How would you read another domain’s cookie without some feature that explicitly allows it, like the Chrome feature in question?
Re:Get Ready for New SameSite=None; Secure Cookie Settings by Thorrez on Friday October 25, 2019 @12:34AM (#21351916)
Oh, you're right there isn't a distinction, for some reason I thought there was.