Brian Inglis via tz wrote:
I have my own leap-seconds.* hash, updated, and expiry date checker/ extractor as IERS did not always get the data correct either, with latest IERS and NIST values:
Yes, that happened when the IERS folks started providing a leap second file, but it's been going smoothly now for some years.
$ leapsec-sha.sh /etc/leap-seconds.listleapsec-sha.sh:/etc/leap-seconds.list:modified 2025-01-07 expires 2025-12-28 # File expires on 28 December 2025$ leapsec-sha.sh leap-seconds.3676924800leapsec-sha.sh:leap-seconds.3676924800:modified 2016-07-08 expires 2026-06-28 # File expires on: 28 June 2026so NIST expiry is correct presuming no leap second is announced in the upcoming July Bulletin C #70,
Yes, presuming, but that's not authoritative right now.
... but the overall file format, update date, and NTP time suffix are defined in the ntp-keygen(1) section "Cryptographic Data Files", such that the date and suffix should be that of the file creation (as a new file should be created with a new suffix for each update).
That's also how I understand it. See also my next reply to Tim. Martin -- Martin Burnicki Senior Software Engineer Email: martin.burni...@meinberg.de Phone: +49 5281 9309-414 Linkedin: https://www.linkedin.com/in/martinburnicki/ MEINBERG Funkuhren GmbH & Co. KG Lange Wand 9 31812 Bad Pyrmont, Germany Registry Court: Amtsgericht Hannover 17 HRA 100322Managing Directors: Natalie Meinberg, Daniel Boldt, Andre Hartmann, Heiko Gerstung
Websites: https://www.meinberg.de https://www.meinbergglobal.com Meinberg - The Synchronization Experts.
OpenPGP_signature.asc
Description: OpenPGP digital signature
