874
edits
Labs/Jetpack/JEP/29: Difference between revisions
Jump to navigation
Jump to search
→Privilege Separation: added more justification for this feature as per Jono's feedback
(→Capability Inference: more) |
(→Privilege Separation: added more justification for this feature as per Jono's feedback) |
||
| Line 85: | Line 85: | ||
manifest. The Jetpack can communicate with its Boosters via a simple | manifest. The Jetpack can communicate with its Boosters via a simple | ||
JSON-based message-passing protocol. | JSON-based message-passing protocol. | ||
The concept of Boosters is analogous to the privilege separation functionality many operating systems provide, whereby one highly-privileged process may fork into two separate processes, one of which drops its privileges, and the two communicate via a pipe or socket pair. For examples, see Wikipedia's article on [http://en.wikipedia.org/wiki/Privilege_separation privilege separation]. | |||
It's expected that Boosters won't need to be used by the majority of Jetpacks: they're essentially a mechanism that allows complex Jetpacks which require lots of capabilities to be able to segment their functionality into separate sandboxes. | |||
Boosters are accessible through the <tt>jetpack.boosters</tt> | Boosters are accessible through the <tt>jetpack.boosters</tt> | ||