Closed
Bug 1004011
Opened 11 years ago
Closed 9 years ago
Support SECCOMP_FILTER_TSYNC if available
Categories
(Core :: Security: Process Sandboxing, defect)
Tracking
()
RESOLVED
FIXED
mozilla43
Tracking | Status | |
---|---|---|
firefox43 | --- | fixed |
People
(Reporter: jld, Assigned: jld)
References
(Blocks 1 open bug)
Details
Attachments
(1 file, 1 obsolete file)
(deleted),
patch
|
kang
:
review+
|
Details | Diff | Splinter Review |
There are Linux kernel changes that have been sent upstream (but not yet accepted) from Chromium to allow atomically applying seccomp filters to all threads in a process: https://lkml.org/lkml/2014/4/17/637
Chromium already has code to do this, intended for use on Android: http://git.chromium.org/gitweb/?p=chromium/src.git;a=commitdiff;h=8c215f5b965930c1faa004834491e4e11c6b26d8
It would be nice if we could use this where available (and, perhaps, backport the patches to our own seccomp-enabled B2G devices) instead of our current signal-based approach.
Assignee | ||
Comment 1•10 years ago
|
||
Move process sandboxing bugs to the new Bugzilla component.
(Sorry for the bugspam; filter on 3c21328c-8cfb-4819-9d88-f6e965067350.)
Component: Security → Security: Process Sandboxing
Assignee | ||
Updated•10 years ago
|
Blocks: pid-namespaces
Assignee | ||
Updated•9 years ago
|
Assignee | ||
Comment 2•9 years ago
|
||
WIP; tested locally on nexus5-l and Ubuntu 14.04; will r? when/if it passes Try.
Assignee | ||
Comment 3•9 years ago
|
||
The last patch made chrooting not work, which is bad. This fixes that, does a little cleanup, and adds some more assertions.
Attachment #8644528 -
Attachment is obsolete: true
Attachment #8646659 -
Flags: review?(gdestuynder)
Attachment #8646659 -
Flags: review?(gdestuynder) → review+
Assignee | ||
Comment 4•9 years ago
|
||
Keywords: checkin-needed
Keywords: checkin-needed
Comment 6•9 years ago
|
||
Status: NEW → RESOLVED
Closed: 9 years ago
status-firefox43:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla43
Assignee | ||
Updated•9 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•