r9 - 2013-02-26 - 13:36:36 - SteveKosteckeYou are here: NTP >  Servers Web > ServerForm > AccessPolicy > RestrictedAccess
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.8p10 was released on 21 March 2017. It addresses 6 medum- and 5 low-severity security issues, 4 informational security topics, 15 bugfixes, and contains other improvements over 4.2.8p9.

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.

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:

  • NotificationMessage
  • 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.

Usage Guidelines

The following usage guidelines apply to Restricted Access Time Servers unless modified by the Time Server Operator:

  1. iburst may be used
  2. burst may not be used
  3. minpoll/maxpoll may not be changed below the defaults of 64 seconds and 1024 seconds respectively
  4. Clients should honor the KOD message
  5. 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

Related Topics: OpenAccess, ClosedAccess, AccessPolicy

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r9 < r8 < r7 < r6 < r5 | 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-2017 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