#1496 HIGH Trial-2: OLPC public key needs to be in the manufacturing data for OFW, and exposed up through Linux to user space

[Zarro Boogs per Child]

#1496: OLPC public key needs to be in the manufacturing data for OFW, and exposed
up through Linux to user space
----------------------------------+-----------------------------------------
  Reporter:  jg                   |       Owner:  wmb at firmworks.com
      Type:  task                 |      Status:  assigned         
  Priority:  high                 |   Milestone:  Trial-2          
 Component:  ofw - open firmware  |     Version:                   
Resolution:                       |    Keywords:  security         
  Verified:  0                    |  
----------------------------------+-----------------------------------------
Changes (by wmb at firmworks.com):

  * owner:  Luna => wmb at firmworks.com
  * status:  new => assigned
  * component:  manufacturing process => ofw - open firmware

Comment:

 I have been discussing this whole public key issue with Ivan.  The current
 thinking is that the public key does not need differ from country to
 country.  That being the case, it makes more sense to embed the PK in OFW,
 instead of putting it in the manufacturing data.

 The only current "client" of the PK is secure firmware update, which means
 that nothing outside of OFW needs to see the PK except perhaps for
 diagnostic purposes.

 Consequently, we should just wait until OFW integrates the secure update
 feature and incorporate the PK in OFW as part of that effort.  The
 milestone remains Trial-2, but the responsibility is now solely in the OFW
 domain.  No need for manufacturing support at the present time.

-- 
Ticket URL: <http://dev.laptop.org/ticket/1496#comment:8>
One Laptop Per Child <http://laptop.org/>