5,705
edits
Changes
Jump to navigation
Jump to search
Line 150:
Line 150: + +
Platform Team/Server Kit/sugar-server (view source)
Revision as of 14:34, 11 November 2011
, 14:34, 11 November 2011→Security issue with backups after re-flashing XOs
* got re-flashed with not keeping client side identities, like Sugar profile private key;
* got re-flashed with not keeping client side identities, like Sugar profile private key;
* the XO wants to restore Journal content from previous backups, but from school server point of view, it is regular registration request from new XO that provide the same serial number that existing registration uses.
* the XO wants to restore Journal content from previous backups, but from school server point of view, it is regular registration request from new XO that provide the same serial number that existing registration uses.
Since this usecase is common for the current XO deployments, sugar-server will process a workaround with permitting such re-registration to let people do restore after re-flashing, even if private key is lost. This will happen only for XO laptops, for the rest case, workflow is [[#UUID_per_Sugar_user|regular]].
== Configuration ==
== Configuration ==