Open
Bug 1360244
Opened 7 years ago
Updated 2 years ago
Review secomp-bpf polices against Chromium
Categories
(Core :: Security: Process Sandboxing, enhancement, P3)
Tracking
()
NEW
People
(Reporter: gcp, Assigned: jld)
Details
(Whiteboard: sb+)
https://docs.google.com/spreadsheets/d/12wk_5n5PDzgqXCjmCUnblsXw5QdR5gGYroBxtCrYVBU/edit#gid=841503896 Review the above against current Chromium, check which apply to web content processes. Also check restrictions on syscall arguments versus ours.
Reporter | ||
Updated•7 years ago
|
Whiteboard: sb?
Assignee | ||
Updated•7 years ago
|
Summary: Review secomp-bfp polices against Chromium → Review secomp-bpf polices against Chromium
Updated•7 years ago
|
Assignee: nobody → jld
Whiteboard: sb? → sblc3
Updated•7 years ago
|
status-firefox57:
affected → ---
Updated•7 years ago
|
Priority: -- → P2
Whiteboard: sblc3 → sb+
Comment 1•6 years ago
|
||
Moving to p3 because no activity for at least 1 year(s). See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•