Changes

* {{Code|uuid}}, user's identity got after registration on a server;

* {{Code|uuid}}, user's identity got after registration on a server;

* {{Code|serial}}, serial number of hardware Sugar user is running on, e.g., serial number of a XO laptop;

* {{Code|machine-serial}}, serial number of hardware Sugar user is running on, e.g., serial number of a XO laptop;

* {{Code|machine-uuid}}, UUID value of hardware Sugar user is running on, e.g., UUID of a XO laptop;

* {{Code|pubkey}}, SSH public key, this is the exact line that needs to be placed as-is to {{Code|~/.ssh/authorized_keys}} file; note that OLPC XS operates with striped version of public keys.

* {{Code|pubkey}}, SSH public key, this is the exact line that needs to be placed as-is to {{Code|~/.ssh/authorized_keys}} file; note that OLPC XS operates with striped version of public keys.

* {{Code|nickname}}, user's Sugar nick name;

* {{Code|nickname}}, user's Sugar nick name;

* {{Code|serial}}, machine's serial number, makes special sense only for XO anti-thief support and [[#Hardware_based_model|hardware based]] identity model,

* {{Code|machine-serial}}, machine's serial number, makes special sense only for XO anti-thief support and [[#Hardware_based_model|hardware based]] identity model,

* {{Code|machine-uuid}}, machine's UUID value, makes special sense only for XO anti-thief support,

* {{Code|pubkey}}, SSH public key passed as-is.

* {{Code|pubkey}}, SSH public key passed as-is.

  GET '''/client/lease'''?serial=''SERIAL''

  GET '''/client/lease'''?serial=''SERIAL''

Get OLPC anti-thief lease for specified XO's serial number.o

Get OLPC anti-thief lease for specified XO's serial number.

The resulting dictionary, contains:

The resulting dictionary, contains:

* valid SSH public key,

* valid SSH public key,

* valid serial number, i.e., serial number that school server is aware about, e.g., there is an activation lease.

* valid machine serial number, i.e., serial number that school server is aware about, e.g., there is an activation lease.

After re-flashing a XO (with loosing private key), it is possible to re-register user with uploading new public key. See [[#Vulnerabilities|below]] for related vulnerability issues.

After re-flashing a XO (with loosing private key), it is possible to re-register user with uploading new public key. See [[#Vulnerabilities|below]] for related vulnerability issues.