Closed
Bug 1228117
Opened 9 years ago
Closed 3 years ago
Determine security policy for DTD loads
Categories
(Core :: DOM: Security, defect, P3)
Core
DOM: Security
Tracking
()
RESOLVED
DUPLICATE
of bug 467035
People
(Reporter: ckerschb, Unassigned)
References
Details
(4 keywords, Whiteboard: [domsecurity-backlog2])
No description provided.
|
Reporter | |
Updated•9 years ago
|
|
|
Reporter | |
Updated•8 years ago
|
Whiteboard: [domsecurity-active]
|
|
Reporter | |
Comment 1•8 years ago
|
||
Have to put this into the backlog for now.
Status: ASSIGNED → NEW
Priority: -- → P2
Whiteboard: [domsecurity-active] → [domsecurity-backlog]
|
|
Reporter | |
Updated•8 years ago
|
Assignee: ckerschb → nobody
|
|
Reporter | |
Updated•8 years ago
|
Priority: P2 → P3
Whiteboard: [domsecurity-backlog] → [domsecurity-backlog2]
|
||
Comment 2•3 years ago
|
||
Christoph, what is left to do here? Could you please provide more context?
Flags: needinfo?(ckerschb)
|
|
Reporter | |
Comment 3•3 years ago
|
||
Not providing a description in the bug is obviously never a smart choice :-(
Anyway, that bug was filed more than 5 years ago as a follow up to Bug 1228116. In the meantime Bug 467035 took care of the problem and even removed the comment in the nsContentSecurityManager but apparently has not closed out this bug.
Long story short, I'll mark this bug as a duplicate of Bug 467035.
Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(ckerschb)
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•