Closed
Bug 1521878
Opened 6 years ago
Closed 6 years ago
Principal serialization fallback consistency
Categories
(Core :: DOM: Security, enhancement)
Tracking
()
RESOLVED
FIXED
mozilla67
| Tracking | Status | |
|---|---|---|
| firefox67 | --- | fixed |
People
(Reporter: jkt, Assigned: jkt)
References
Details
(Whiteboard: [domsecurity-active])
Attachments
(1 file)
In many places we are calling (de)serializePrincipal and not safely falling back to a (de)serialized principal and instead letting other call sites in the stack catch the errors.
We should have consistency in the call sites that serialize then try again to create a serialized null principal.
|
Assignee | |
Updated•6 years ago
|
Whiteboard: [domsecurity-active]
|
|
Assignee | |
Comment 1•6 years ago
|
||
Pushed by jkingston@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/dc037803ceb6
Have fallback consistency for (de)serialization of principals. r=ckerschb
|
||
Comment 3•6 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 6 years ago
status-firefox67:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla67
|
|
Assignee | |
Updated•5 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•