Closed
Bug 934476
Opened 12 years ago
Closed 11 years ago
Make sure Chromium sandbox isn't used for plugins initially
Categories
(Core :: Security, defect)
Tracking
()
RESOLVED
FIXED
mozilla33
People
(Reporter: bbondy, Assigned: TimAbraldes)
References
Details
Make plugins not use chromimum sandbox or now even when MOZ_CONTENT_SANDBOX is defined. Currently if you force it defined and do a tbpl push a lot of tests will fail. We initially only want this for content processes.
|
Reporter | |
Updated•11 years ago
|
Assignee: netzen → nobody
|
Assignee | |
Comment 1•11 years ago
|
||
If we can set the policy for plugin processes to be unrestrictive enough, perhaps we can make those tbpl tests pass and not have to special-case plugin processes to avoid the sandbox.
Assignee: nobody → tabraldes
Status: NEW → ASSIGNED
|
|
Assignee | |
Comment 2•11 years ago
|
||
This landed as part of bug 985252 [1][2]
[1] https://mxr.mozilla.org/mozilla-central/source/ipc/glue/GeckoChildProcessHost.cpp?rev=be05446d4fd2#759
[2] https://mxr.mozilla.org/mozilla-central/source/ipc/glue/GeckoChildProcessHost.cpp?rev=be05446d4fd2#818
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•