Re: [time-nuts] On the IETF leap-seconds.list SHA1

2017-12-21 Thread Didier Juges
I am so glad that my laziness has a new name that does not sound nearly as bad as the original one... I will be sure to remember that next time I do my "self appraisal". Merry Christmas everyone (I know I am early but my clock is fast...) Didier KO4BB On Thu, Dec 21, 2017 at 2:08 AM, Mike

Re: [time-nuts] On the IETF leap-seconds.list SHA1

2017-12-21 Thread Martin Burnicki
Am 21.12.2017 um 07:37 schrieb Hal Murray: >> I am still unable to access the NIST ftp-site linked earlier in this thread. > > There have been several URLs mentioned. > > If you want: > ftp://time.nist.gov/pub/leap-seconds.list > Try > ftp://ftp.nist.gov/pub/time/leap-seconds.list > > Any

Re: [time-nuts] On the IETF leap-seconds.list SHA1

2017-12-21 Thread Mike Cook
> Le 21 déc. 2017 à 07:01, Anders Wallin a écrit : > >> >>> For the Paris Observatory and USNO files my program agrees with the SHA1s >>> in the files. >>> For the IETF file there seems to be one byte, a "0" at the start of the >>> third group of 8 hex characters

Re: [time-nuts] On the IETF leap-seconds.list SHA1

2017-12-20 Thread Hal Murray
> I am still unable to access the NIST ftp-site linked earlier in this thread. There have been several URLs mentioned. If you want: ftp://time.nist.gov/pub/leap-seconds.list Try ftp://ftp.nist.gov/pub/time/leap-seconds.list Any attempts at web/ftp-ing to time.nist.gov are very likely to

Re: [time-nuts] On the IETF leap-seconds.list SHA1

2017-12-20 Thread Anders Wallin
> > > For the Paris Observatory and USNO files my program agrees with the SHA1s > > in the files. > > For the IETF file there seems to be one byte, a "0" at the start of the > > third group of 8 hex characters missing. > >This is not a bug but a « feature ». From the ntpd leap hash checking >

Re: [time-nuts] On the IETF leap-seconds.list SHA1

2017-12-20 Thread Mike Cook
> Le 20 déc. 2017 à 12:51, Anders Wallin a écrit : > > Hi all, > So I'm doing the typical Wednesday thing you might do, that is writing a > small script for checking the SHA1 checksum in leap-seconds.list files. > I came up with [1] which produces output [2]. > >

Re: [time-nuts] On the IETF leap-seconds.list SHA1

2017-12-20 Thread Martin Burnicki
Martin Burnicki wrote: > See also a summary at > https://www.meinbergglobal.com/download/burnicki/the_ntp_leap_second_file.pdf I saw that the leapseconds file provided by USNO is outdated, and FTP access to the NIST sites has changed, so I've just updated the PDF accordingly. Martin

Re: [time-nuts] On the IETF leap-seconds.list SHA1

2017-12-20 Thread Martin Burnicki
Martin Burnicki wrote: > According to an email from Judah Levine (NIST) the current version of > the leap second file is available via anonymous FTP from all public NIST > NTP servers. A list of these servers and the status of each server is > available at > http://tf.nist.gov/tf-cgi/servers.cgi >

Re: [time-nuts] On the IETF leap-seconds.list SHA1

2017-12-20 Thread Martin Burnicki
Anders Wallin wrote: > Thanks, > I added the IANA URL to my list, and sent them an e-mail. > I can't seem to reach the nist ftp-server - does it work for anyone? Please note the global address time.nist.gov is resolved to a number of public servers in a round-robin sequence. Some of the servers

Re: [time-nuts] On the IETF leap-seconds.list SHA1

2017-12-20 Thread Martin Burnicki
John Hawkinson wrote: > Umm, the presence of a copy of the IANA TZ distribution at > https://www.ietf.org/timezones/ is not evidence of an "IETF leap-seconds > list." This is bizarre, and probably a web server configuration error that > even exists. The IETF is not involved in this list. I

Re: [time-nuts] On the IETF leap-seconds.list SHA1

2017-12-20 Thread Anders Wallin
Thanks, I added the IANA URL to my list, and sent them an e-mail. I can't seem to reach the nist ftp-server - does it work for anyone? I re-named the output.txt so the link in my previous e-mail won't work. The output now shows on the github repo frontpage:

Re: [time-nuts] On the IETF leap-seconds.list SHA1

2017-12-20 Thread John Hawkinson
Umm, the presence of a copy of the IANA TZ distribution at https://www.ietf.org/timezones/ is not evidence of an "IETF leap-seconds list." This is bizarre, and probably a web server configuration error that even exists. The IETF is not involved in this list. I guess this shows why Google is an