Feature roadmap/Activation lease security

Feature subcategory		Is part of::Category:Security, activation and deployability
Requesters		{{#arraymap:Peru, Ethiopia (especially last point), Uruguay?|,|x|Requested by::x}}
Requirements		Overview The controlling idea is that when an XO is stolen it will stop working after a time (activation lease time) unless it contacts a re-leasing server (usually a School Server). For example, if an XO is stolen and taken away from its school server, after the expiration of the lease time it will no longer boot up. If the XO is stolen but still comes within range of its school server, it can still be prevented from booting if the XO information (probably serial number) has been added to a black list on the XS. If the laptop is stolen, and doesn't contact its local school server within some period time (activation lease time) the XO will no longer boot (I call this "deactivated"). Si se roba el XO y el XO no se contacta a su servidor (XS) local de la escuela dentro de una cierta hora del perío (tiempo del arriendo) el XO va a encender (boot) (llamo este " deactivated"). When the XO boots up and contacts the XS, its lease time is extended. e.g. if the activation lease time is 30 days and it starts on November 1, then the XO boots up on November 20 and contacts the XS, it will continue functioning without contacting the XS until December 20. Cuando el XO arranca y entra en contacto con el XS, su tiempo del arriendo es extendido. e.g. si el tiempo del arriendo de la activaciós 30 dí y comienza el 1 de noviembre, despuéel XO arranca el 20 de noviembre y entra en contacto con el XS, écontinuaráuncionando sin entrar en contacto con el XS hasta el 20 de diciembre. Optionally as set by the administrator, if an XO is deactivated and tries to boot up when in the vicinity of its controlling school server, then it will boot unless it has been added to a blacklist. The blacklist is a list of XOs (by serial number?) which has been entered in to the school server by its administrator. That is, the activation lease time will be automatically extended whenever the XO contacts its controlling XS, unless it has been entered in the black list. Opcionalmente como fija por el administrador, si un XO se desactiva e intenta boot cuando esta en la vecindad de su servidor de la escuela que controla, despuéboot a menos que se haya agregado a una lista negra. La lista negra es una lista de XOs (por nú de serie?) cuáha sido entrado adentro al servidor de la escuela por su administrador. Es decir, el tiempo del arriendo de la activacióeráutomácamente cuando el XO entra en contacto con su XS que controla, a menos que no se haya inscrito en la lista negra. Must allow setting of the activation lease time by the deployment lead (user interface required). That is, they can set it for 90 days or whatever they want. The granularity should be at 24 hours and be from 1 day to never expire. Must allow setting this once for a recurring interval (e.g. XO leases expire every 60 days). Debe permitir el ajuste del tiempo del arriendo de la activacióor del despliegue (interfaz utilizador requerido). Es decir, pueden fijarlo por 90 dí o lo que quieren. La granulosidad debe ser en 24 horas y ser a partir de 1 dínunca a expirar. Debe permitir el fijar de esto una vez para un intervalo el repetirse (e.g. los arriendos de XO expiran cada 60 dí). Must not be possible for the user to set the date on the laptop to keep it within the lease period or to force it to outside the lease management. This might mean you cannot change the date or there is no root access, or it might mean an alternate time source is used. Necesidad no ser posible para que el usuario fije la fecha en el ordenador portál para guardarlo dentro del perío del arriendo o para forzarlo fuera de la gerencia del arriendo. Esto pudo significar usted no puede cambiar la fecha o no hay acceso a root, o puede ser que signifique que una fuente alterna del tiempo estátilizada. Must support the same as described above but allow the server which determines the activation to be across the Internet. The lease management server can be in a data center managed by the deployment or on a server managed by OLPC. Apoye iguales como se describe anteriormente pero permita el servidor que determina la activacióara estar a travédel Internet. El servidor de la gerencia del arriendo puede estar en un centro de datos manejado por el despliegue o en un servidor manejado por OLPC. Must support the same requirement as described above but allow the reset of the activation to be done via USB key. That is, when an XO's lease expires, it must be booted with the USB key containing a special code. This can be done before it expires to extend the lease. Apoye el mismo requisito como se describe anteriormente pero permita que el reajuste de la activacióea hecho víllave del USB. Es decir, cuando el arriendo de un XO se expira, ése debe boot con la llave del USB que contiene un cóo especial. Esto puede ser hecha antes de que expire para extender el arriendo. Should support the ability for an XS to continuously generate new leases every nnn time as set by the user (e.g. every 2 weeks). This will allow an XS to be placed in a school and then it does not need Internet access or anyone from outside the school to continuously update the lease times. Should support a GUI accessible from the XO which is password protected and encrypted (aka no passwords in the clear across the network/wireless). This GUI will allow a user in the school to enter an XO by serial number or better by name and have that XO added to the blacklist (see above, essentially its lease is not renewed). See also write up on "Actual security requirements": User:Mstone/Commentaries/Security_1 and Server side "Blueprint" at: http://wiki.laptop.org/go/XS_Blueprints:Lease_and_update_server
Specification		* <trac>4043</trac> Firmware Key and Signature Formats#Version 2 http://dev.laptop.org/~cscott/joyride-api/bitfrost.leases.crypto-module.html http://lists.laptop.org/pipermail/security/2008-June/000441.html
Owners		{{#arraymap:|,|x|Contact person::User:x}} Please indicate developers or champions supporting this request
Priority		not indicated
Helps deployability?		not indicated
Target for 9.1?		not indicated