FoxInABox: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 23: | Line 23: | ||
* {{ok|Burn down permission list}} | * {{ok|Burn down permission list}} | ||
Permission Burndown List: | Permission Burndown List (see {{bug|918680}} for details): | ||
{ | <bugzilla> | ||
{ | |||
"status": ["NEW", "UNCONFIRMED", "RESOLVED", "REOPENED"], | |||
"blocks": "918680", | |||
"include_fields": "last_change_time, id, summary, status, assigned_to" | |||
} | |||
</bugzilla> | |||
</td><td> | </td><td> | ||
Revision as of 21:36, 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:
FxOS / B2G
Permission Burndown List (see bug 918680 for details): 13 Total; 1 Open (7.69%); 12 Resolved (92.31%); 0 Verified (0%);
|
Linux Firefox
Permission List:
| ||
Windows Firefox
Permission List:
|
MacOS X Firefox
Permission List:
|
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