Bug 1235569 (securing-remote-newtab)

[Meta] Securing remote about:newtab

RESOLVED WONTFIX

Status

()

defect
RESOLVED WONTFIX
4 years ago
2 years ago

People

(Reporter: franziskus, Assigned: franziskus)

Tracking

(Depends on 2 bugs, Blocks 1 bug, {meta})

Trunk
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(firefox46 affected)

Details

(Whiteboard: [domsecurity-meta])

This is a meta bug to keep track of security mechanisms for the remote about:newtab page.
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.)
we're working with the b2g folks together on this
Keywords: meta
Whiteboard: [domsecurity-meta]
Assignee: nobody → franziskuskiefer
Status: NEW → ASSIGNED
Status: ASSIGNED → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.