r1 - 2009-01-23 - 23:55:59 - JohannesMaximilianKuehnYou are here: NTP >  Dev Web > RefclockUpdateCheck
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.

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.

Refclock Update Check

About two weeks ago (January 7th 2009) someone reported that ntpdate refuses to sync with ntp.nmi.nl. An interesting point here was that ntpdate refused to sync with this server while ntpd and sntp accepted it.

The cause that made ntpdate refuse this server's packets was that this server's ref clock hasn't been updated for more than 1 day. ntpdate got a sanity check which checks if the server's refclock has been updated during the last 24 hours according to the reference clock update timestamp.

In principle this checks looks like a wise thing to do. What do you guys think about this check? Shouldn't ntpd/sntp check for that in general (with a user defineable threshold and a sane default)?

-- JohannesMaximilianKuehn - 23 Jan 2009


Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | More topic actions
SSL security by CAcert
Get the CAcert Root Certificate
This site is powered by the TWiki collaboration platform
IPv6 Ready
Copyright & 1999-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding the site? Send feedback