Closed Bug 1179061 Opened 9 years ago Closed 8 years ago

Create CSP tests for signed packages

Categories

(Core :: DOM: Security, defect, P2)

Product:
Core
Component:
DOM: Security
Type:
defect

Tracking

()

Status:
RESOLVED WONTFIX
Milestone:
FxOS-S8 (02Oct)
Project Flags:
tracking-b2g backlog

People

(Reporter: pauljt, Assigned: ethan)

References

Details

We should start creating some CSP tests for signed packages. Separating this bug from implementation of package CSP so we can start this in parallel.
Priority: -- → P1
blocking-b2g: --- → 2.5+
Assignee: nobody → ettseng
Status: NEW → ASSIGNED
Before writing CSP test for signed packages, we have to at least add default CSP policies for signed packages.
Thus, this bug should be blocked by Bug 1179060 - Apply a default CSP for signed packaged content.
Depends on: 1179060
Target Milestone: --- → FxOS-S6 (04Sep)
Priority: P1 → P2
Target Milestone: FxOS-S6 (04Sep) → FxOS-S8 (02Oct)
[Tracking Requested - why for this release]:

This bug as part of New Security Model is not a 2.5 blocker as New Sec is not part of 2.5 now.

Removing 2.5 blocker flag.
blocking-b2g: 2.5+ → ---
tracking-b2g: --- → backlog
Paul, seems B2G specific as well, can we close this one or no?
Flags: needinfo?(ptheriault)
The same as bug 1179060.
Even if we plan to continue NSEC v2, signed package would no longer be an option.
No reason so work on this bug.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Flags: needinfo?(ptheriault)
Resolution: --- → WONTFIX
(In reply to Ethan Tseng [:ethan] from comment #4)
> No reason so work on this bug.
            ^^
typo.
No reason to work on this bug.
You need to log in before you can comment on or make changes to this bug.