#1731 HIGH Retriag: Sugar should provide activities (at least python ones) with temp file facilities

[Zarro Boogs per Child]

#1731: Sugar should provide activities (at least python ones) with temp file
facilities
--------------------------+-------------------------------------------------
  Reporter:  tomeu        |       Owner:  mstone           
      Type:  enhancement  |      Status:  new              
  Priority:  high         |   Milestone:  Retriage, Please!
 Component:  sugar        |     Version:                   
Resolution:               |    Keywords:  security, sugar  
  Verified:  0            |  
--------------------------+-------------------------------------------------
Changes (by mstone):

 * cc: coderanger, mburns (removed)
 * cc: marco, tomeu, MurielGodoi (added)
  * owner:  tomeu => mstone
  * priority:  normal => high
  * milestone:  Opportunity => Retriage, Please!


Comment:

 Turns out that putting activity instances into a separate namespace from
 Sugar is a bad idea; people really seem to want to be able to communicate
 with sugar through their tmp-dir. Fortunately, this is one wish that we
 can safely grant.

 Solution: leave activities in the same namespace as Sugar but be sure to
 mount the tmpfs you're going to give to the activity inside an
 appropriately permissioned gate-dir that sugar controls. This way Sugar
 and the activity share access to a RAM-backed space that no one else can
 get to, the size of the space is still restricted, and we remain agnostic
 about when the space will actually be reclaimed (which is important since
 the activity instance life-cycle is still not adequately pinned down).

-- 
Ticket URL: <http://dev.laptop.org/ticket/1731#comment:6>
One Laptop Per Child <http://dev.laptop.org>
OLPC bug tracking system