Closed
Bug 1235569
(securing-remote-newtab)
Opened 9 years ago
Closed 7 years ago
[Meta] Securing remote about:newtab
Categories
(Core :: DOM: Security, defect)
Core
DOM: Security
Tracking
()
RESOLVED
WONTFIX
Tracking | Status | |
---|---|---|
firefox46 | --- | affected |
People
(Reporter: franziskus, Assigned: franziskus)
References
(Depends on 2 open bugs)
Details
(Keywords: meta, Whiteboard: [domsecurity-meta])
This is a meta bug to keep track of security mechanisms for the remote about:newtab page.
Assignee | ||
Updated•9 years ago
|
Depends on: Content-Signature
Comment 1•9 years ago
|
||
At one point there was some offline discussion of whether the streaming package / manifest signing machinery from B2G would be usable instead of Content-Signature, once we'd realized there was some possible duplication of effort there — what was the result of that?
(I'm not arguing for either side here, but it would be nice to have the rationale recorded.)
Assignee | ||
Updated•9 years ago
|
See Also: → newtab-fallback
Assignee | ||
Comment 2•9 years ago
|
||
we're working with the b2g folks together on this
Updated•8 years ago
|
Assignee: nobody → franziskuskiefer
Status: NEW → ASSIGNED
Assignee | ||
Updated•7 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•