Changes

Registry items might contains following keys:

Registry items might contains following keys:

* {{Code|uuid}}, a hash value of the {{Code|pubkey}} (produced the same way as JID values in Sugar Shell), an unique and short identity of [[#UUID per Sugar user|particular Sugar user]];

* {{Code|uuid}}, a hash value of the {{Code|pubkey}} treated as an unique and short [[#UUID per Sugar user|user's identity];

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

* {{Code|serial}}, serial number of hardware Sugar user is running on, e.g., serial number 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.

=== UUID per Sugar user ===

=== UUID per Sugar user ===

Sugar-server treats UUID values as unique identities of particular Sugar users, i.e., not unique identities of particular hardware that Sugar users run on (like OLPC XS does). If people need to keep access to their personal data, uploaded to the server, they need to keep private key, from {{Code|~/.sugar/default/owner.key}} file, and the UUID value, they got after registration on a server, as a an id or registration.

Sugar-server treats UUID values as unique identities of particular Sugar users, i.e., not unique identities of particular hardware that Sugar users run on (like OLPC XS does). UUID values are being calculated from users' pubkey, in the same way as JID values in Sugar Shell. If people need to keep access to their personal data, uploaded to the server, they need to keep private key, from {{Code|~/.sugar/default/owner.key}} file, e.g., while hardware migration or reinstalling.

== Services ==

== Services ==