Rainbow: Difference between revisions

Latest revision as of 21:00, 26 November 2011

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

Rainbow :: git :: sources :: rainbow-0.8.6.tar.bz2 :: announcement

The Bitfrost security specification argues that existing desktop security conventions do not meet the security needs:

of adventurous kids in 1-1 computing programs,
of the technical staff who help maintain such initiatives, and
of the political constituencies which determine where such programs take place.

The most serious inadequacy of such systems is that they force end-users to take unnecessary security risks (for example, giving all programs a user runs access to the network, to auto-start facilities, and to other programs' data files) while simultaneously denying users the opportunity to do things which can be done safely but which were not anticipated by the system administrator (notably, installing new software or modifying the local system.)

Consequently, we wrote Rainbow.

Rainbow is an isolation shell. This means two things:

shell: Rainbow runs programs on behalf of humans and programs. Rainbow provides those programs with a suitable environment: places in which temporary and persistent data can be stored, environment variables to identify those places, etc.
isolation: People and programs should use Rainbow when they want to isolate programs from other programs and important system resources. "Isolation" is already a familiar concept to most UNIX programmers: many system daemons already operate using their own unique UID and/or GID, and most have private places in which they store their configuration. Rainbow generalizes and extends this paradigm by providing every program it runs with a unique identity, with private storage, with pre-configured resource usage limits, etc.

At the moment, Rainbow only knows how to provide the same primitive form of filesystem and signal isolation that competent sysadmins provide to users of multi-user Unix shell servers.

However, contributions are welcome, particularly contributions which advance existing plans.

Information about rainbow-0.8.*

current situation: feature, design, and implementation notes for rainbow-0.8.*
installation instructions for rainbow-0.8.*
testing instructions for rainbow-0.8.*
next steps!
demo ideas

Other Information

notes for Activity Developers, for Sugar 0.82 and rainbow-0.7.*
historical design comparisons, for rainbow-0.6.*, -0.7.*, and -0.8.*
curiosities

Subpages

(Titles in italics redirect to another page.)

@@ Line 1: / Line 1: @@
-{{OLPC}}
-{{developers}}
 {{translations}}
+<noinclude>{{Google Translations}}
-<noinclude>{{ GoogleTrans-en | es =show | bg =show | zh-CN =show | zh-TW =show | hr =show | cs =show | da =show | nl =show | fi =show | fr =show | de =show | el =show | hi =show | it =show | ja =show | ko =show | no =show | pl =show | pt =show | ro =show | ru =show | sv =show }}</noinclude>
+[[Category:Security]]
-== Introduction ==
+</noinclude>{{Rainbow page}}
-''[http://dev.laptop.org/git/users/mstone/security git] :: [http://dev.laptop.org/~mstone/releases/SOURCES sources] :: [http://dev.laptop.org/~mstone/releases/SOURCES/rainbow-0.8.2.tar.bz2 rainbow-0.8.2.tar.bz2]''
+The [[OLPC Bitfrost|Bitfrost]] security specification argues that existing desktop security conventions do not meet the security needs:
-The [[OLPC Bitfrost|Bitfrost]] security specification argues that existing desktop security conventions do not meet the security needs of adventurous kids in 1-1 computing programs, of the technical staff who help maintain such initiatives, and of the political constituencies which determine where such programs take place. The most serious inadequacy of such systems is that they force end-users to take unnecessary security risks (for example, giving all programs a user runs access to the network, to auto-start facilities, and to other programs' data files) while simultaneously denying users the opportunity to do things which can be done safely but which were not anticipated by the system administrator (notably, installing new software or modifying the local system.) Consequently, [[Security credits|we]] wrote Rainbow.
+* of adventurous kids in 1-1 computing programs,
+* of the technical staff who help maintain such initiatives, and
+* of the political constituencies which determine where such programs take place.
+The most serious inadequacy of such systems is that they force end-users to take unnecessary security risks (for example, giving all programs a user runs access to the network, to auto-start facilities, and to other programs' data files) while simultaneously denying users the opportunity to do things which can be done safely but which were not anticipated by the system administrator (notably, installing new software or modifying the local system.)
+Consequently, [[Security credits#Activity Isolation|we]] wrote [http://dev.laptop.org/git/users/mstone/security/tree/rainbow Rainbow].
 Rainbow is an isolation shell. This means two things:
-# ''shell'': Rainbow runs programs on behalf of humans and programs.
+# ''shell'': Rainbow runs programs on behalf of humans and programs.  Rainbow provides those programs with a suitable environment:  places in which temporary and persistent data can be stored, environment variables to identify those places, etc.
-# ''isolation'': People and programs should use Rainbow when they want to isolate programs from other programs and important system resources.
+# ''isolation'': People and programs should use Rainbow when they want to isolate programs from other programs and important system resources.  "Isolation" is already a familiar concept to most UNIX programmers:  many system daemons already operate using their own unique UID and/or GID, and most have private places in which they store their configuration.  Rainbow generalizes and extends this paradigm by providing every program it runs with a unique identity, with private storage, with pre-configured resource usage limits, etc.
 At the moment, Rainbow only knows how to provide the same primitive form of filesystem and signal isolation that competent sysadmins provide to users of multi-user Unix shell servers.
-However, '''[[Security#Contributions|contributions]]''' are welcome, particularly contributions which advance [[#Next Steps|existing plans]].
+However, '''[[Security#Contributions|contributions]]''' are welcome, particularly contributions which advance [[Rainbow/Next Steps|existing plans]].
+'''Information about rainbow-0.8.*'''
-== For Activity Developers ==
+* [[Rainbow/Current Situation|current situation]]: feature, design, and implementation notes for rainbow-0.8.*
-When the user asks Sugar to start your activity, Rainbow is the software which actually asks the Linux kernel to do the 'starting'. However, in order to achieve the security goals described in Bitfrost, it places some restrictions on your software. You can find out more about these restrictions in the [[Low-level Activity API#Security|low-level activity api]] documentation. (In the future, the [[Sugar almanac]] may also contain some similar information).
+* [[Rainbow/Installation Instructions|installation instructions]] for rainbow-0.8.*
+* [[Rainbow/Testing|testing]] instructions for rainbow-0.8.*
+* [[Rainbow/Next Steps|next steps!]]
+* [[Rainbow/Demo Ideas|demo ideas]]
+'''Other Information'''
-=== Disabling Rainbow for Testing ===
+* notes for [[Rainbow/Information for Activity Developers|Activity Developers]], for Sugar 0.82 and rainbow-0.7.*
-Sugar's use of Rainbow can be trivially disabled by running
+* [[Rainbow/Historical Designs|historical design comparisons]], for rainbow-0.6.*, -0.7.*, and -0.8.*
+* [[Rainbow/Curiosities|curiosities]]
- rm /etc/olpc-security
+==Subpages==
+(Titles in ''italics'' redirect to another page.){{Special:PrefixIndex/{{PAGENAME}}/}}
-as root. It can be re-enabled by running
- touch /etc/olpc-security
-also as root.
-=== Responding to Isolation ===
-The [[Low-level Activity API#Security|Low-level Activity API's security section]] explains some basic ways that activities should respond to being isolated, particularly with regard to isolation from the file system.
-=== Customizing Isolation ===
-The [[Activity bundles#activity/permissions.info|Activity bundles' activity/permissions.info]] documentation offer some hints on how activities may currently customize the isolation provided by rainbow.
-== Design ==
-Rainbow has been implemented according to three designs to date.
-=== 0.8-series ===
-The 0.8 series is designed as an [http://en.wikipedia.org/wiki/Chain_loading "exec-wrapper"]. The "rainbow-run" wrapper is receives control from the shell, performs any requested isolation steps, then hands control over to isolated program. This way, rainbow can be used from [http://freedesktop.org freedesktop.org] [http://standards.freedesktop.org/desktop-entry-spec/latest/ .desktop] launcher files, from the command-line, and from custom graphical shells like [[Sugar]] with equal ease.
-=== 0.7-series ===
-The 0.7 series was designed as a privileged [http://www.freedesktop.org/wiki/Software/dbus dbus] [http://en.wikipedia.org/wiki/Daemon_(computer_software) daemon]. Sugar calls into this daemon when it wants to launch activities. An advantage of having a daemon is that the daemon can cache the results of expensive computations like python module loading. The problem with the daemon is that it consumes extra memory and that its caching behavior can cause many frustrating bugs.
-=== 0.6-series ===
-The first implementation of rainbow (and of [[olpc-update]]) used a containerization technology called [http://linux-vserver.org VServer] to implement extensive isolation including network and CPU usage limits. Unfortunately, these early implementations revealed fundamental race conditions in the custom vserver patches provided to OLPC and the OLPC kernel team was unwilling to support the patches. [[User:Mstone|Michael Stone]] created a new design outline, written up in [http://dev.laptop.org/git?p=security;a=blob;f=rainbow.txt;hb=HEAD rainbow.txt] which explained how Bitfrost could be approached without vserver and vserver was removed from the kernel.
-== Installation ==
-Last updated: [[User:Mstone|Michael Stone]] 21:36, 27 February 2009 (UTC)
-=== 0.8-series ===
-The basic idea is to install rainbow, either
-'''from a distro package:'''
-* Fedora >= 10: yum install rainbow
-* Ubuntu: [https://launchpad.net/~codewiz/+archive/ppa Bernie's PPA] contains some basic rainbow packages which you can install.
-* Other: Install rainbow from source or help others by packaging it for your distro!
-'''from source:'''
- RAINBOW=rainbow-0.8.2
- wget http://dev.laptop.org/~mstone/releases/SOURCES/$RAINBOW.tar.bz2
- tar xf $RAINBOW.tar.bz2 && cd $RAINBOW
- make -f Makefile.build build
- sudo make -f Makefile.build install
-'''from a unified builder or image:'''
-like [http://sugarlabs.org/go/DevelopmentTeam/Jhbuild sugar-jhbuild] or [http://sugarlabs.org/go/Sugar_on_a_Stick Sugar on a Stick] (SoaS). ''(nb: future work)''
-'''setup''':
-In order for rainbow to function, you need to inject its users and groups into the system by running:
- sudo /bin/sed -i -e s/^passwd:/passwd:\ rainbow/ /etc/nsswitch.conf
- sudo /bin/sed -i -e s/^group:/group:\ rainbow/ /etc/nsswitch.conf
-Currently, you also need to change the D-Bus configuration to allow users besides the
-owner to access the session bus. This might allow others on the same machine
-to control your applications and access your data, so only do this change if you're
-fine with that (e.g. no one else or only trusted ones using your computer).
-You need to add the following line to /etc/dbus-1/session.conf inside the
-<policy context="default"> section:
-    <allow user="*"/>
-Congratulations. You are now ready to test rainbow.
-== Testing ==
-Rainbow is easy to test in chroots, for example, those created by [http://fedoraproject.org/wiki/Projects/Mock mock]. See [http://dev.laptop.org/git/users/mstone/test-rainbow test-rainbow] and, in particular,this [http://dev.laptop.org/git?p=users/mstone/test-rainbow;a=blob;f=suggestions;hb=HEAD small multi-user test script].
-To test it on a regular system, you might [[#Installation|install it]], then run something like:
-  sudo rainbow-run -q -s /var/spool/rainbow/2 -c / -f 0 -f 1 -f 2 -u `whoami` -i nice -- /bin/bash
-This will drop you into an isolated bash session in which you can play.
-''NB: If you want to isolate graphical software, then you're going to need to use a helper program like <tt>rainbow-sugarize</tt> to provide an X cookie, access to the D-Bus session bus, etc.''
-Obviously, please contribute more automated tests, helpers, and [[Reporting bugs|bug reports]]!
-== Next Steps ==
-Last updated: [[User:Mstone|Michael Stone]] 17:48, 1 March 2009 (UTC)
-; Integration with sugar-0.86
-: There are a couple of small impedance mismatches that will need to be overcome; e.g. sugar needs a way to kill an activity, a way to garbage-collect dead jails, and a way to reuse a jail when an activity is to be resumed.
-: We also need to find a way to make dbus session buses happy accepting connections from per-bus groups of users. The current plan is to implement a "group_pattern" authorization attribute and to have libnss_rainbow synthesize the appropriate group memberships. We'll start with positive and negative automated tests.
-; P_NETWORK
-: We'd like to have the option to restrict a program's access to the network. James Morris suggests that we check out [http://lxc.sourceforge.net unshare(CLONE_NEWNET)].
-: See [[Isolation LSM]], http://lkml.org/lkml/2009/1/7/18, and http://lkml.org/lkml/2009/1/7/613 for some other approaches.
-; P_DOCUMENT*
-: Requested by Gary C. Martin. To implement this, we need to put some authorization gates in the datastore, then somehow record which data should be accessible to which activities. (Or maybe we could do it all with ACLs?)
-: See [[Olpcfs]] and [[Journal reloaded]] for some other approaches.
-; P_X
-: -- we'll start by trying out XSECURITY (i.e. by making activities untrusted clients) and see where that leaves us. Then on to XACE as per [http://lists.laptop.org/pipermail/security/2008-April/000390.html previous discussion]
-:: -- unfortunately, it seems (c.f. ssh man page) that most apps break when you treat them as untrusted clients. Hmm.
-== Demo Ideas ==
-* (paraphrase): "The insight behind Rainbow is that the problem of isolating an operator from his/her programs is similar to the problem of isolating users of a shared server from one another and from root." -- ''C. Scott Ananian''
-* "I see the cool parts [of Rainbow] as (1) per-instance isolation, (2) isolation without virtualization, and (3) isolation using the uid mechanisms. All three are unique and impressive." ''-- Ben Schwartz''
-: ''(NB: Actually, lots of other people have played with these ideas. [http://plash.beasts.org/wiki/ plash] is a compelling example.)''
-Ideas:
-* Give people an isolated Terminal to play in.
-* Show off rlimits with a fork-bomb.
-* Show off filesystem protections -- rm -rf, restriction of readable dirs, etc.
-== Items of Historical Interest ==
-* [http://dev.laptop.org/git?p=security;a=blob;f=rainbow/README;hb=HEAD README] - A description of the original scope and design of Rainbow.
-* [http://dev.laptop.org/git?p=security;a=blob;f=rainbow/NOTES;hb=HEAD Notes] - Notes on design and hurdles in developing Rainbow.
-* [[Rainbow/DataStore Access]] - thoughts on datastore access mechanisms, superseded by [[Olpcfs]].
-* [http://lists.laptop.org/pipermail/security/2008-January/000370.html "Why not SELinux?"]
-* [http://lists.laptop.org/pipermail/sugar/2007-November/003725.html "Bitfrost Compliance for Update.1" announcement mail]
-* {{Ticket|2732}}, {{Ticket|2906}}, {{Ticket|4184}} - influential tickets in the history of rainbow
-[[Category:Software]]
-[[Category:Security]]

Rainbow: Difference between revisions

Latest revision as of 21:00, 26 November 2011

Subpages

Navigation menu

Search