[OLPC Security] find_bundle, etc in util/bundle.py

[Michael Stone]

Marcus,

I'm ambivalent on this issue; in fact, the patch that I just submitted
to @sugar for review contains some hunks explicitly designed to allow
rainbow to launch bundles without parsing the activity.info file at all.

I certainly agree that we need security records for each
activity-version that we want to launch - but it's not clear to me that
my initial idea that these be encoded in the activity.info file was a
good one. In particular, the activity.info format is not particularly
good at recording the firewall rules.

More recent work on this subject is recorded at 

  users/krstic/installer 

Michael


On Mon, Nov 05, 2007 at 02:38:54PM -0500, Marcus Leech wrote:
> I'm slowly hacking-in some code that can read capabilities in from the
> activity.info file in an activity bundle.
> 
> It seems to me that having the entire config object (not just the
> "Activity" section) available to any piece of the
>   stack during launch would be very beneficial.  For example, in
> "Bundle" it picks specific things out of the config
>   object, for use by "other things".  But it seems to me that having the
> entire config object available to those "other things"
>   would be extremely helpful.
> 
> Right now, I hacked in a call to find_bundle in stages/sugar.py:launch  
> but I fear some generality is lacking by doing this.
> 
> 
> 



> _______________________________________________
> Security mailing list
> Security at lists.laptop.org
> http://lists.laptop.org/listinfo/security