Partial key autonomy: Difference between revisions

From OLPC
Jump to navigation Jump to search
mNo edit summary
mNo edit summary
Line 1: Line 1:
'''Proposal 1: Maintain the firmware and dev-key status quo while permitting everything else to be modified.'''
'''Proposal:'''


For each party P who so requests,
For each party P who so requests,

Revision as of 23:00, 24 December 2008

Proposal 1: Maintain the firmware and dev-key status quo while permitting everything else to be modified.

For each party P who so requests,

  1. ask party P to generate
  2. generate a firmware, initramfs, and olpc-update which contain the public values of these keys.
    • alternately, provide the keys through /ofw and rewrite the initramfs and olpc-update code to read /ofw
  3. have OLPC return a signed version of the customized firmware to party P.

By installing the signed customized firmware on a stock machine, party P will be able to autonomously provide builds and activation leases and will be able to execute or modify the theft-deterrence protocol for that machine. Party P may also further delegate these abilities, e.g. with version-2 lease signatures. OLPC will retain responsibility for providing developer keys and firmware updates.