Collection stick

From OLPC
Revision as of 01:20, 24 June 2010 by Quozl (talk | contribs) (add reference to canonical documentation in case of trouble disabling security)
Jump to: navigation, search

Making a collection key

You'll need a FAT-formatted or FAT32-formatted USB storage device for this, as well as a computer with internet access. The USB storage device does not need to be empty.

  1. Create a /boot directory in the root of your USB storage device. If such a directory already exists, it should be empty. (Exception: if you have already used this collector key to gather data from a number of XOs, there may be a laptops.dat file in the /boot directory. Do not delete laptops.dat.)
  2. On the computer with internet access, Actos.zip and Runos.zip (source code) into that /boot directory. You should now have 2 files (3, if you have laptops.dat in a /boot directory on the root of your USB storage device.

Collecting with a collection key

For each XO you need a key for:

  1. Make sure the XO is powered off.
  2. Plug the USB storage device into the XO, then power it on.
  3. You will see a graphical "XO" screen and then a short message like "SHFxxxxxxxx nnnnnnnnnnnnnnn; Laptop data recorded successfully". The XO will then power itself off or otherwise indicate that it is done.
  4. Remove the USB storage device from the XO.

When you have finished this process on all the XOs you need developer keys for, plug the USB storage device into the computer with internet access and attach the /laptops.dat file from the USB storage device to an email to help at laptop dot org indicating whether you want a developer key or an activation key.

Making an unlock key

You will receive back one or two files from OLPC after submitting your laptops.dat file (this may take several days). Here is what to do once you get these files.

  1. Get a USB storage device. This can be your old collection key; you will have to rename the /boot directory to something else like /collection. If you don't do this, your laptop will just re-run the collection script.
  2. If you requested a developer key: You will get a file called develop.sig. Make a directory called security/ in the root directory of your USB storage device and copy this file into it.
  3. If you requested an activation key: You will get a file called lease.sig. Copy this file into the root directory of your USB storage device.

You are now ready to use your unlock key.

Unlocking with an unlock key

For each XO you are trying to unlock:

  1. Make sure the XO is powered off.
  2. Plug the USB storage device into the XO, then power it on.
  3. That's it!
  4. Note that this process only unlocks your XO once - if you want to unlock your XO permanently without needing to plug in the USB storage device every time you boot, see #Permanently unlocking with an unlock key.

Permanently unlocking with an unlock key

Activation keys

No action is required. Activation keys are automatically copied to /security/lease.sig on your XO. Keep the activation key around (or copy it to your school server) in case you later need to reflash the XO.

Developer keys

When the XO boots the first time, you should see a textual prompt, which you will see within the first few seconds of booting (along with a short countdown to give you time to hit the Escape key). This is your indication that the developer key has been found.

To permanently disable secure booting, press Escape and type "disable-security", then power cycle and repeat that command. See Activation and developer keys.

The developer key is not automatically copied to your laptop's internal flash memory. You can do that by copying security/develop.sig from the USB flash drive into /security/develop.sig on the XO. You'll need to be root in a Terminal activity to do that.

sudo cp /media/USBDRIVE/security/develop.sig /security/develop.sig