Re: [time-nuts] On the IETF leap-seconds.list SHA1
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 Cook wrote: > > A case of « economy of thought » . > ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] On the IETF leap-seconds.list SHA1
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 attempts at web/ftp-ing to time.nist.gov are very likely to not work. > Don't waste your time trying. That's their rotating DNS for NTP servers. > > I think the original plan was to have all the NTP sites mirror the FTP info > but it didn't work out. > > Indeed, originally the NIST version of the leap second file was made publicly available via FTP access to each of the NIST time servers. However, according to a note on https://www.nist.gov/pml/time-and-frequency-division/services/internet-time-service-its FTP access to the time servers has been phased out, and all of the public files including the leap second file have been moved to these public FTP sites: ftp://ftp.nist.gov/pub/time (directory listing) ftp://ftp.nist.gov/pub/time/leap-seconds.list (leap second file) and ftp://ftp.boulder.nist.gov/pub/time (directory listing) ftp://ftp.boulder.nist.gov/pub/time/leap-seconds.list (leap second file) Martin ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
Re: [time-nuts] On the IETF leap-seconds.list SHA1
> 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 missing. >> >> This is not a bug but a « feature ». From the ntpd leap hash checking >> code: >> >> * The NIST code creating the hash writes them out as 5 hex integers >> * without leading zeros. >> >> Still, it a little unorthodox and complicates the code. >> > > Ha! Thanks for explaining this. > Indeed I find writing out the SHA-1 in groups of 8 characters without > leading zeroes quite surprising and undocumented. > The comments in leap-seconds.list about the SHA-1 refer to a /sha or > /pub/sha folder - is that generic information on the SHA-1 or is there any > inidication of the 8-char/leading-zeroes convention there? > I quickly looked at FIPS-180 but didn't find anything about leading zeros > there. My guess is that during testing the NIST guy who created the program to print the list never hit the case where the integer created a less than 8 character hex output. Probably used %8x instead of %08x in his format statement, or something analog if it was not C. A case of « economy of thought » . > > I am still unable to access the NIST ftp-site linked earlier in this thread. > > Anders > ___ > time-nuts mailing list -- time-nuts@febo.com > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. "The power of accurate observation is commonly called cynicism by those who have not got it. » George Bernard Shaw ___ time-nuts mailing list -- time-nuts@febo.com To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
