On Tue, 10 Feb 2015 06:52:24 -0700 Theo de Raadt wrote: > > > Document that RFC 5905 (ie. NTP protocol) has a limit which will be > > > hit before Y2038. > > > > RFC868? > > No. > > Apparently you cannot use google or such before you send a mail. > _______________________________________________________________
Correct leap seconds. This should be used only when synchronizing to a server which does not correctly account for leap seconds. Use SNTP (RFC 5905) instead of the RFC 868 time protocol. This is the default. Use an RFC 868 TCP protocol server instead of SNTP. This protocol is obsolete as it is not capable of representing dates past January 19, 2038 03:14:07 GMT. ________________________________________________________________ Looks like I just grabbed the latest commit from 21 months ago without checking the date and commit text. I assumed that whilst 5905 allows if I remember rightly 128bit? or a mode with the 2038 bug you were referring to RFC 868 from that patch? > > p.s. Do you think there is *any* chance of getting long long in as > > rfc5905 is sometimes used as a reference for other time format > > standards? > > None. Because then it would probably be a new RFC. I thought it was going to be, Sorry.
