Rainbow: Difference between revisions

From OLPC
Jump to navigation Jump to search
No edit summary
No edit summary
Line 19: Line 19:
* [http://dev.laptop.org/git?p=security;a=blob;f=rainbow/README;h=5e7f1051b43292a7af8bb0c6ae72987ad5d89b18;hb=HEAD README] - A description of the scope and design of Rainbow.
* [http://dev.laptop.org/git?p=security;a=blob;f=rainbow/README;h=5e7f1051b43292a7af8bb0c6ae72987ad5d89b18;hb=HEAD README] - A description of the scope and design of Rainbow.
* [http://dev.laptop.org/git?p=security;a=blob;f=rainbow/NOTES;h=5277468b760c7d92d6713f5c0b6939ebf0978f2b;hb=HEAD Notes] - Useful notes on design and hurdles in developing Rainbow.
* [http://dev.laptop.org/git?p=security;a=blob;f=rainbow/NOTES;h=5277468b760c7d92d6713f5c0b6939ebf0978f2b;hb=HEAD Notes] - Useful notes on design and hurdles in developing Rainbow.
* [[Rainbow/DataStore Access]]



[[category:software]]
[[category:software]]

Revision as of 18:40, 5 November 2007

  english | español HowTo [ID# 75529]  +/-  


Rainbow implements the isolation shell implicitly described in the Bitfrost security specification. This means that it isolates activities (and eventually system services) that it is asked to run from one another and the rest of the system.

Rainbow implements this isolation by generating a new uid (and perhaps a new gid) for each program it is asked to run. Running each activity as a separate user means that standard Unix access checks can be used as the primary 'gate' to control the visibility of activity-driven side-effects like reading from or writing to files or devices or signalling other processes.

Finally, "rainbow" is also the name of the build branch into which this isolation shell is being integrated.

Installing

To install Rainbow, either directly install a build from the Rainbow build branch or use the network updater to migrate to a build from that branch.

 # olpc-update rainbow-NNN

Resources