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.
Restrict Access Time Server
A restricted access time server does not require prior arrangements before use but has some restrictions on its use in addition to the usage guidlines listed below. These restrictions include, but are not limited to:
- Service only to clients within a specified ServiceArea
- Service only to certain types of institutions
- Maximum number of clients
- Minimum poll interval
Users are reponsible for reviewing the list entry for a RestrictedAccess
server prior to using it.
The following usage guidelines apply to Restricted Access Time Servers unless modified by the Time Server Operator:
Related Topics: OpenAccess
iburst may be used
burst may not be used
minpoll/maxpoll may not be changed below the defaults of 64 seconds and 1024 seconds respectively
- Clients should honor the
- Time Server IP addresses and/or hostnames may not be hard-coded in any hardware, firmware, or software without advance explicit written permission from the time server operator