#11563 NORM Not Tri: inaccuracy with conversion to unix timestamps

[Zarro Boogs per Child]

#11563: inaccuracy with conversion to unix timestamps
---------------------------------+------------------------------------------
 Reporter:  dsd                  |                 Owner:  wmb at firmworks.com
     Type:  defect               |                Status:  new              
 Priority:  normal               |             Milestone:  Not Triaged      
Component:  ofw - open firmware  |               Version:  not specified    
 Keywords:                       |           Next_action:  never set        
 Verified:  0                    |   Deployment_affected:                   
Blockedby:                       |              Blocking:                   
---------------------------------+------------------------------------------
 We are seeing a problem with rtcreset.sig verification when dealing with
 certain dates. The "current RTC time" field in the rtcreset.sig file
 matches what is listed in the rtc-timestamp chosen property, but the
 firmware incorrectly complains that there is a mismatch.

 I have narrowed this down to a bug relating to conversion to/from unix
 timestamps. This demonstrates the issue:

 {{{
 " 20131209T000350Z" decode-timestamp >unix-seconds unix-seconds>
 }}}

 The returned date is 8th December 2013 - it should be the 9th, as it was
 in the input.

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