874
edits
Labs/Jetpack/JEP/29: Difference between revisions
Jump to navigation
Jump to search
→Privilege Separation: added more
(→Privilege Separation: added more justification for this feature as per Jono's feedback) |
(→Privilege Separation: added more) |
||
| Line 89: | Line 89: | ||
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. | 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. | ||
Note that because the security characteristics of Boosters are specified statically before run-time, it's entirely possible for the main Jetpack to have no privileges, and instead simply facilitate communication between separate semi-privileged Boosters. For instance, one Booster could be responsible for interacting with the filesystem, while another could be responsible for interacting with the network, and so forth. | |||
Boosters are accessible through the <tt>jetpack.boosters</tt> | Boosters are accessible through the <tt>jetpack.boosters</tt> | ||