Add carveout for NullPrincipal when asserting if explicit CSP and CSP on Principal are equal
Categories
(Core :: DOM: Security, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: ckerschb, Assigned: ckerschb)
References
Details
(Whiteboard: [domsecurity-active])
Attachments
(2 files)
12.79 KB,
patch
|
Details | Diff | Splinter Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review |
Using a clean profile do:
- Navigate to data:application/json,["visit%20http://mozilla.org"]
- It should open the JSON Viewer, with a mozilla.org link, click on it
Assertion in nsDocshell fires exhibiting that the explicit CSP and the CSP on the triggeringPrincipal are not equal.
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 1•6 years ago
|
||
Jonathan, Gijs, I found the problem why the assertion in nsDoShell is firing, but I am not sure if it's worth landing my patch given that we are so close to land Bug 965637 (which is ready for review today). Probably we might open a can of worms.
In detail:
We have not been serializing the CSP within the Principal for NullPrincipals. Please note that we have never been doing that and the problem disappears after Bug 965637, which would remove all the code we would add within this patch.
I think it might be the better solution to add a carveout to the assertion within nsDocshell and just do not assert for NullPrincipals so the update within Bug 1540069 can land.
What do you think?
Comment 2•6 years ago
|
||
Assuming bug 965637 lands soon that wfm.
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 3•6 years ago
|
||
Comment 5•6 years ago
|
||
bugherder |
Description
•