NTP users are strongly urged to take immediate action to ensure that their NTP daemons are not susceptible to being used in distributed denial-of-service (DDoS) attacks. Please also take this opportunity to defeat denial-of-service attacks by implementing Ingress and Egress filtering through BCP38.
ntp-4.2.8p15 was released on 23 June 2020. It addresses 1 medium-severity security issue in ntpd, and provides 13 non-security bugfixes over 4.2.8p13.
Are you using Autokey in production? If so, please contact Harlan - he's got some questions for you.
" graphics="on"}% See ConfiguringIrigRefclocksDev for discussion of this topic.
6.1.7. Configuring Irig Refclocks
Vanilla IRIG-B carries only the number of
the day (0-365) within the current year, but doesn't tell you which year
IEEE 1344 compliant IRIG-B contains the Gregorian year.
One site reported a problem after the beginning of a new year, as NTP was listening to the IRIG-B signal but was not getting the year data.
The problem was traced to a misconfigured NTP time server that was
ignoring the 1344 data (which contains the Gregorian year) in the IRIG-B
signal from the GPS receiver.
[Exactly how was
misconfigured to cause this problem? I don't see how that is possible...]
On reading the NTP logs, you could just feel the rising frustration in
the system administrator as he killed and restarted the NTP daemon, to
no avail - the year was still wrong. Eventually, he just shut NTP off
and set the computer clock by hand. This worked well enough for a
while, but after two or three months the computer clock had drifted
enough to cause communications to be lost (because message timestamps
were so far off that the receiver threw the messages away).
The solution was to update the maintenance manuals to ensure that the
1344 information was both sent (by the GPS receiver) and received (by
the NTP time server).
[Again, exactly what needed to be done to
? By my read of the
code we are expecting the gregorian year in the decoded data stream.]