FoxInABox: Difference between revisions
Jump to navigation
Jump to search
| Line 28: | Line 28: | ||
"status": ["NEW", "UNCONFIRMED", "RESOLVED", "REOPENED"], | "status": ["NEW", "UNCONFIRMED", "RESOLVED", "REOPENED"], | ||
"blocks": "918680", | "blocks": "918680", | ||
"include_fields": " | "include_fields": "id, summary, status" | ||
} | } | ||
</bugzilla> | </bugzilla> | ||
</td><td> | </td><td style="text-align:top"> | ||
=== Linux Firefox === | === Linux Firefox === | ||
Revision as of 21:37, 23 October 2013
Documentation
Status
We have a plan. Take the e10s code, slap the Chromium sandbox around the content process, and get AdBlockPlus working with it.
FoxInABox/ThingsThatShouldWork
Tracking: bug 925570.
Platform specific:
Additional Pieces
These are some things that we need to attack next (after a basic sandbox).
- GPU remoting (TBD)
- Accessibility support
- Addon support path
- Process Model (evolving? 2? Per-Tab?)
- Incremental tightening plan
- Child process resource limits
- DevTools support
Resources
Sandboxing
- Features/Security/Low_rights_Firefox -- bug 730956
- Ian's sandboxing page
- Servo
- Chromium Sandbox
- seccomp sandboxing on b2g
- Apple's Sandbox guide
Related projects
- Electrolysis
- Embedding/IPCLiteAPI, https://github.com/tmeshkova/mozilla-central
- Native Client on Wikipedia - has links to papers on Native Client's design and use of SFI, as well as papers on SFI itself
- AMO/Squeaky, or Make Addons Awesome
How things work
Who we are
Some folks from the SecurityEngineering team: briansmith, mmc, keeler, grobinson, ckerschb, sid, and bbondy.
- Mailing list: boxing@lists.mozilla.org
- IRC: irc.mozilla.org #boxing