#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:                
-------------------------+--------------------------------------------------

Comment(by cscott):

 Replying to [comment:10 bemasc]:
 > Replying to [comment:9 mstone]
 > If the boot counter is kept in the firmware, and preserved over firmware
 upgrades

 It is not, and cannot be for Gen 1.

 > 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?

 http://wiki.laptop.org/go/Firmware_Key_and_Signature_Formats#Version_2

 This has gone afield, though: the original use case is for *developers* to
 make it easy to follow new releases (from OLPC or Uruguay or whomever) yet
 maintain a set of installed "extra" RPMs.

 Michael's patch, with a simple dev key restriction added, seems the most
 direct means to address this use case at the present time.

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