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.8p13 was released on 07 March 2019. It addresses 1 medium-severity security issue in ntpd, and provides 17 non-security bugfixes and 1 other improvements over 4.2.8p12.

Please see the NTP Security Notice for vulnerability and mitigation details.

---

Are you using Autokey in production? If so, please contact Harlan - he's got some questions for you.

6.1.1. Configuring ATOM (PPS) Refclocks

The ATOM refclock is built by default. Building is enabled/disabled by the option --enable-ATOM or --disable-ATOM in the 'configure' command line, for example: ./configure --enable-ATOM

The driver will look for the PPS signal on /dev/ppsX, where X is the unit number (0-4) on the server 127.127.22.X line in your ntp.conf file.

Note that some refclocks have builtin support for a PPS signal and do not currently use the ATOM driver. See Bug #557 and LoseThePerDriverPPSCode for more information.

Note that the current kernel-mode Windows PPS driver (serialPPS.sys download) does not support inverted polarity on the DCD line - it must be asserted (positive going) on the leading edge of the second.

Related Topics: AtomRefclockUsers