linux-kernel - Re: Bug: Status/Summary of slashdot leap-second crash on new years 2008-2009

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sun, 04 Jan 2009 19:13:21 +1030
From:	David Newall <davidn@...idnewall.com>
To:	Ben Goodger <goodgerster@...il.com>
CC:	Robert Hancock <hancockr@...w.ca>, linux-kernel@...r.kernel.org,
	linasvepstas@...il.com, "Jeffrey J. Kosowsky" <jeff@...owsky.org>,
	MentalMooMan <slashdot@...eshallam.info>,
	Travis Crump <pretzalz@...hhouse.org>, burdell@...ntheinter.net
Subject: Re: Bug: Status/Summary of slashdot leap-second crash on new years
 2008-2009

Ben Goodger wrote:
> 2009/1/3 David Newall <davidn@...idnewall.com>:
>   
>> Shouldn't this be a simple zoneinfo change, whereby the last two seconds
>> of the year (in each timezone) both map to 31dec2008 23:59:59?  That's
>> the way the change has worked in the real world.  Why would ntp or the
>> kernel be involved?
>>     
>
> Actually, the change has worked in the real world with the
> introduction of a new second named 23:59:60

Fine.  However you want to describe that last second is immaterial.  The
point is that diddling the clock is not a true solution.  Take seconds
since epoch for January 1 and subtract the seconds since epoch since the
previous day and if the result isn't 86401 it's wrong.  Is Linux wrong? 
(I gather it is.)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/