#11669 NORM 1.75-so: olpc-update-query cannot tell the difference between a corrupted lease and an unlimited one

[Zarro Boogs per Child]

#11669: olpc-update-query cannot tell the difference between a corrupted lease and
an unlimited one
-----------------------+----------------------------------------------------
 Reporter:  greenfeld  |                 Owner:  martin.langhoff                  
     Type:  defect     |                Status:  new                              
 Priority:  normal     |             Milestone:  1.75-software                    
Component:  distro     |               Version:  Development build as of this date
 Keywords:             |           Next_action:  diagnose                         
 Verified:  0          |   Deployment_affected:                                   
Blockedby:             |              Blocking:                                   
-----------------------+----------------------------------------------------
 olpc-update-query cannot tell the difference between a corrupted lease.sig
 file and one with an unlimited (zero) timestamp.

 However OFW can, and will require the XO to activate itself the next time
 around.

 This was seen in a deployment's image based on 11.3.1 os26-os28.

 Reproduction:
  1. Secure an XO-1.75 to require leases.
  2. Activate said XO intitially.
  3. Overwrite /security/lease.sig with 2 MB of data from /dev/urandom to
 simulate file corruption.
  4. Run "olpc-update-query -v".

 Output of step 4 above:

 {{{
 Querying http://schoolserver/antitheft/1/
 Server time: 20120302T202738Z
 Considering new lease from server
 Current lease expires 00000000T000000Z, new lease expires 20120307T202738Z
 Staying with existing lease
 }}}

-- 
Ticket URL: <http://dev.laptop.org/ticket/11669>
One Laptop Per Child <http://laptop.org/>
OLPC bug tracking system