Closed
Bug 1752333
Opened 4 years ago
Closed 3 years ago
Assert (by default) if a blocklisted preference is accessed from the content process
Categories
(Toolkit :: Preferences, enhancement)
Toolkit
Preferences
Tracking
()
RESOLVED
FIXED
112 Branch
| Tracking | Status | |
|---|---|---|
| firefox112 | --- | fixed |
People
(Reporter: tjr, Assigned: tjr)
References
(Blocks 1 open bug)
Details
Attachments
(1 external file)
No description provided.
| Assignee | ||
Comment 1•4 years ago
|
||
This bug can be used to manage the default-on situation, which is blocked by data-review and legal review over by https://bugzilla.mozilla.org/show_bug.cgi?id=1708798#c26
Summary: Assert if a blocklisted preference is accessed from the content process → Assert (by default) if a blocklisted preference is accessed from the content process
Comment 2•4 years ago
|
||
Tom, do we need anything other than https://phabricator.services.mozilla.com/D141418 for this bug? Thanks!
Flags: needinfo?(tom)
| Assignee | ||
Comment 3•4 years ago
|
||
Yes, we will need to flip fission.omitBlocklistedPrefsInSubprocesses to true-by-default for all branches to enable the actual protection.
We'll also want to enable fission.enforceBlocklistedPrefsInSubprocesses in Nightly/Early Beta at least (ideally all channels) but before we do that we need to keep it opt-in for now while we iterate on Bug 1766866.
Flags: needinfo?(tom)
| Assignee | ||
Comment 4•3 years ago
|
||
Pushed by tritter@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/44a91e08e412
Enable crashing on sanitized pref access in Early Beta r=smaug
Comment 6•3 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 3 years ago
status-firefox112:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 112 Branch
Updated•3 years ago
|
Whiteboard: [sp3]
Updated•3 years ago
|
See Also: → https://mozilla-hub.atlassian.net/browse/SP3-163
Updated•3 years ago
|
See Also: https://mozilla-hub.atlassian.net/browse/SP3-163 →
Whiteboard: [sp3]
You need to log in
before you can comment on or make changes to this bug.
Description
•