Closed Bug 1235569 (securing-remote-newtab) Opened 8 years ago Closed 7 years ago

[Meta] Securing remote about:newtab

Categories

(Core :: DOM: Security, defect)

Product:
Core
Component:
DOM: Security
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX
Tracking Flags:
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.
Depends on: Content-Signature
Depends on: 1235572
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.)
See Also: → newtab-fallback
we're working with the b2g folks together on this
Depends on: 1251152
Depends on: 1255798
Depends on: 1256248
Keywords: meta
Whiteboard: [domsecurity-meta]
Depends on: 1263793
Depends on: 1280905
Assignee: nobody → franziskuskiefer
Status: NEW → ASSIGNED
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.