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.
The
NTP Project uses the following dynamic
DNS-based Black Lists to reduce the amount of spam delivered through our mail server:
- rbl-plus.mail-abuse.org
- blackholes.mail-abuse.org
- zen.spamhaus.org
- cbl.abuseat.org
- list.dsbl.org
- dynablock.njabl.org
- dnsbl.njabl.org
- relays.mail-abuse.org
- nonconfirm.mail-abuse.org
We also maintain internal static black lists of servers or networks that have abused our systems in the past.
If you would like to learn more about what black lists are and how they work, the
WikiPedia article on blacklists is an excellent place to start. You can also look up your IP address or your mail server via any of various different services, including
https://www.mxtoolbox.com/blacklists.aspx, and
https://www.dnsbl.info/advanced.asp, among many others.
See also the main
AntiSpam page which describes various standard anti-spam techniques that are used to protect the ntp.org mail system, of which the black lists mentioned here are just one mechanism.
Please contact our
Postmaster Services Team if you have any further questions regarding the black lists that are used within the ntp.org mail system.
Settings:
Set ALLOWTOPICCHANGE =
NtpPublicServicesProjectStaffGroup