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.
NTP Contact Information
The primary sources of assistance for NTP users are the documentation, this site, the newsgroup and the FAQ. The development mailing lists are not for end-user support. Please use direct e-mail as a last resort.
Bugs, Security Issues, and Suggestions
Tracking of NTP development concerns, including security issues, is done using Bugzilla, an open-source bug tracking system developed by the the Mozilla team. Our Bugzilla is located at bugs.ntp.org
. All users need a unique Bugzilla account, which can be created from the Bugzilla page. Users are encouraged to report bugs or suggest enhancements.
concerning the NTP Reference Implementation may also be reported to firstname.lastname@example.org
. Please report security issues concerning this web-site to email@example.com
Internet Relay Chat
The official NTP IRC channel is #ntp on irc.freenode.net (the Freenode IRC network)
- Keep in mind that the NTP IRC channel participants may not be awake or even at their computer. Please try to leave your IRC client on the channel as long as possible if you do not receive an answer soon after asking your NTP related question.
- Please use ntp.pastebin.com for posting ntp.conf files and command (i.e. 'ntpq -p') output.
- For general IRC usage information, please visit www.irchelp.org or the freenode web page.
Past site contributors