Re-enable same-site schemeful
Categories
(Core :: Networking: Cookies, task, P1)
Tracking
()
People
(Reporter: freddy, Assigned: tschuster)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged])
Attachments
(2 files, 1 obsolete file)
+++ This bug was initially created as a clone and follow-up of Bug #1748693 +++
Bug 1748693 is only a hotfix. This is the second part from bug 1748693 comment 13:
There is still the potential for cookie injection attacks from http://insecure.site.example framing https://good.site.example that "schemeful samesite" (along with "lax by default") was intended to prevent. There are several existing cookie features that https://good.site.example could be using for protection, like secure cookies and cookie prefixes, but "lax by default" is trying to help sites that haven't thought about these issues and schemeful is part of that.
Updated•3 years ago
|
Comment 1•3 years ago
|
||
Note that we've only disabled samesite schemeful on Fx96 at the moment. Is this bug indication that we should be disabling it everywhere until this is resolved?
Comment 2•3 years ago
|
||
I'm wondering if we should put it behind EARLY_BETA_OR_EARLIER for 97+ for the time-being.
Comment 3•3 years ago
|
||
Not sure if we'll be ready to do this for 98 or not, but 97 isn't going to happen.
Updated•3 years ago
|
Reporter | ||
Comment 4•3 years ago
|
||
(In reply to Ryan VanderMeulen [:RyanVM] from comment #1)
Note that we've only disabled samesite schemeful on Fx96 at the moment. Is this bug indication that we should be disabling it everywhere until this is resolved?
I shoulda removed this flag much earlier. This happened in bug 1751435.
Reporter | ||
Comment 5•3 years ago
|
||
Re-enabling this is urgent, but it's not a defect. We won't make Firefox 98 either, so marking that as wontfix.
Assignee | ||
Updated•2 years ago
|
Assignee | ||
Comment 6•2 years ago
|
||
We decided to re-enable network.cookie.sameSite.schemeful
and network.cookie.sameSite.noneRequiresSecure
even without necessarily enabling lax-by-default. This spreads the risks around multiple releases.
Assignee | ||
Comment 7•2 years ago
|
||
Depends on D150600
Assignee | ||
Comment 8•2 years ago
|
||
Depends on D150602
Assignee | ||
Comment 9•2 years ago
|
||
Depends on D150603
Updated•2 years ago
|
Updated•2 years ago
|
Comment 10•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/b1a8adcb9099
https://hg.mozilla.org/mozilla-central/rev/3b7d15317952
https://hg.mozilla.org/mozilla-central/rev/90d51383665c
Assignee | ||
Comment 11•2 years ago
|
||
Release Note Request (optional, but appreciated)
[Why is this notable]: Sites using SameSite=None or different schemes for cookies might break.
[Affects Firefox for Android]: Yes
[Suggested wording]: Cookies with SameSite=None
must now also specify the Secure
attribute. Cookies are now only considered same-site if they use the same scheme (http
or https
). (This is heavily inspired by the docs in MDN below)
[Links (documentation, blog post, etc)]: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie/SameSite
Comment 12•2 years ago
|
||
Added to 104.0a1 release notes https://www.mozilla.org/en-US/firefox/104.0a1/releasenotes/
Assignee | ||
Comment 13•2 years ago
|
||
In bug 1679318 we saw site breakage caused by none-requires-secure. SameSite=None is also less useful without also shipping lax-by-default, because the website can just specify no SameSite attribute at all.
On the schemeful side I realized that with bug 1756213 still missing we are actually missing at least on piece of the implementation, which we should probably ship together.
For now just backing this out completely seems like the easiest way forward.
Assignee | ||
Updated•2 years ago
|
Comment 14•2 years ago
|
||
Backed out as requested by dev: https://hg.mozilla.org/integration/autoland/rev/56ff9d9fe4233290960d6e035a72ecef1374127f
Assignee | ||
Comment 15•2 years ago
|
||
Hi Dianna, this was backed out, so we should probably also update the release notes.
Comment 16•2 years ago
|
||
Hi, Removed from 104.0a1 relnotes. Thank you!
Updated•2 years ago
|
Comment 17•2 years ago
|
||
Backout merged to central: https://hg.mozilla.org/mozilla-central/rev/56ff9d9fe4233290960d6e035a72ecef1374127f
Assignee | ||
Comment 18•2 years ago
|
||
Re-using this bug to only land same-site schemeful.
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Comment 19•2 years ago
|
||
Comment 20•2 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/28957fbb64d5
https://hg.mozilla.org/mozilla-central/rev/ff07f346788a
Comment 21•2 years ago
|
||
:tom can you revise the relnote with the new patch?
Assignee | ||
Comment 22•2 years ago
|
||
This "feature" by itself is more of a bug fix and probably doesn't require a release note.
Updated•2 years ago
|
Description
•