Open
Bug 1291502
Opened 8 years ago
Updated 2 years ago
Improve media plugin filesystem access sandbox policy failure modes
Categories
(Core :: Security: Process Sandboxing, defect)
Tracking
()
NEW
Tracking | Status | |
---|---|---|
firefox51 | --- | affected |
People
(Reporter: jld, Unassigned)
References
Details
(Whiteboard: sb+)
In bug 1290633 I changed the GMP sandbox policy to fail most unexpected open()s without crashing, in order to avoid the crash reporter always recursively crashing and never getting a crash dump. This still isn't ideal because we don't get the metadata, but also it means we won't notice any other unexpected opens that happen outside of crash handling. Once we have a capable enough filesystem broker, we could give GMP processes the same “sandboxed temp dir” capability as content processes and use that; if/when we do, we can effectively revert bug 1290633. A slightly separate problem: I could have done something like strstr() the path for "GeckoChildCrash" and soft-failed only those, but I was also concerned that this might happen again for some other path/filename that *is* opened during crash handling and not realize it, the same way bug 1290633 went unnoticed at first. So it would be nice if there were something like a global atomic flag set while crashing (including non-sandbox-induced) to try to avoid crash recursion, but that might be more of a feature request for the Breakpad Integration component.
Updated•8 years ago
|
Whiteboard: sb+
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•