| 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
| ||
|
Date: Mon, 05 Jan 2009 10:31:28 +1030 From: David Newall <davidn@...idnewall.com> To: Chris Adams <cmadams@...aay.net> CC: linux-kernel@...r.kernel.org Subject: Re: Bug: Status/Summary of slashdot leap-second crash on new years 2008-2009 Chris Adams wrote: > Once upon a time, David Newall <davidn@...idnewall.com> said: > >> No. Exactly the contrary. I'm saying that through use of zoneinfo, for >> example, no kernel support is required for leap seconds. And! this >> provides correct results for seconds-between two dates. >> > > Again: zoneinfo provides offset from UTC. Leap seconds are changes in > UTC itself, not time zones, so zoneinfo can't handle that. > Yes, but zoneinfo ALSO provides support for leap seconds. Do read man zic for specific details. > Please go read Google, Wikipedia, and NTP lists. I think you particularly mean NTP. I think your reasoning is that because NTP's timestamp doesn't include leap seconds, and because we all like to use NTP to synchronise our clocks, Linux has to make up the difference. But there is an alternative; which is for the NTP client to insert those missing leap seconds, which number it can get from zoneinfo. Epoch remains the start of 1978; seconds between any two dates included leap-seconds and no special kernel support is required. -- 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/
Powered by blists - more mailing lists