#4196 BLOC First D: Method for obtaining developer keys needed.

[Zarro Boogs per Child]

#4196: Method for obtaining developer keys needed.
-----------------------+----------------------------------------------------
  Reporter:  cjb       |       Owner:  cscott                
      Type:  defect    |      Status:  new                   
  Priority:  blocker   |   Milestone:  First Deployment, V1.0
 Component:  security  |     Version:                        
Resolution:            |    Keywords:                        
  Verified:  0         |  
-----------------------+----------------------------------------------------
Changes (by cscott):

 * cc: mstone (added)


Comment:

 We do actually have a method for generating developer keys; it is in my
 codebase.

 I just haven't closed this bug because I haven't set up the 'production'
 version on activation.laptop.org yet (it's still living at xo.cscott.net).
 But I agree this is a blocker.

 A related issue is that a developer key *must* trump the 'stolen' flag --
 which it does at the moment.  Escrowing the developer keys is sufficient
 to prevent a future malicious OLPC from declaring all machines 'stolen'
 just before going out of business, and so makes the stolen-lock compatible
 with the restrictions of the GPLv2,3.  (Anything we do w/o a developer key
 is GPL-compatible, as long as the developer key-ed software is completely
 permissive.)

 (Michael -- is there a trac # for 'obtain FSF letter' yet?  It should be
 referenced here.)

-- 
Ticket URL: <https://dev.laptop.org/ticket/4196#comment:2>
One Laptop Per Child <https://dev.laptop.org>
OLPC bug tracking system