Date: Thu, 2 Jul 2015 15:22:37 +0100 From: RW <rwmaillists@googlemail.com> To: freebsd-security@freebsd.org Subject: Re: Leap Second Message-ID: <20150702152237.42ba56cf@gumby.homeunix.com> In-Reply-To: <21908.39278.416719.875140@hergotha.csail.mit.edu> References: <CAA3htvuv0Emy5SazXzYNZegKzS-Z4=tc3ua8Ca6GMgeTj99n7A@mail.gmail.com> <1435154274.964221.306546033.052903CD@webmail.messagingengine.com> <86bnfwxa4m.fsf@nine.des.no> <1435758941.105242.312562265.3103CECB@webmail.messagingengine.com> <CAK-wPOjqZUPnWSbgXYt%2Bghu1BHUK7E=dUVU=oW8%2B0p7ywzN4Wg@mail.gmail.com> <20150701202728.GA9532@server.rulingia.com> <21908.39278.416719.875140@hergotha.csail.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 1 Jul 2015 21:52:46 -0400 Garrett Wollman wrote: > <<On Thu, 2 Jul 2015 06:27:28 +1000, Peter Jeremy > <peter@rulingia.com> said: > > > ntpd(8) has provision for specifying a leapsecond file which > > presumably makes it leap-second aware. I haven't looked into the > > details. > > The current NTP protocol, as implemented by ntpd, distributes > leap-second information if provided. This information may be provided > by higher-stratum (upstream) NTP servers, or by using the "leapfile" > configuration statement in ntp.conf to specify a local copy of the > leapseconds file in NIST/USNO format. No such file is provided by > default. We could easily do so, but shouldn't, because that file > would take precedence over the leap indicator learned from > higher-stratum servers, and that's not desirable for clients. I thought this sounded unlikely because the files have an explicit expiry date, so I looked it up. Apparently before 4.2.8 ntpd doesn't ignore expired leap-second files, so they continue to take precedence over fresh information from other servers.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150702152237.42ba56cf>