#6432 NORM Never A: Autoinstallation of RPMs

[Zarro Boogs per Child]

#6432: Autoinstallation of RPMs
-------------------------+--------------------------------------------------
   Reporter:  cscott     |       Owner:  cscott        
       Type:  defect     |      Status:  new           
   Priority:  normal     |   Milestone:  Never Assigned
  Component:  distro     |     Version:                
 Resolution:             |    Keywords:                
Next_action:  never set  |    Verified:  0             
  Blockedby:             |    Blocking:                
-------------------------+--------------------------------------------------
Changes (by bemasc):

 * cc: bmschwar at fas.harvard.edu (removed)
 * cc: bemasc (added)


Comment:

 Replying to [comment:9 mstone]

 If the boot counter is kept in the firmware, and preserved over firmware
 upgrades, then this seems like a secure option, provided that activation
 is required first.  It seems very fragile though.  What if I accidentally
 reboot a machine before completing the unsigned RPM installation?

 The underlying statement here is: we will allow the deployers to make any
 modifications they choose to the software on the machine.  If that's the
 case, why not just delegate signing authority so that deployers can create
 new custom images and RPMs for their machines at any time?

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