NTP users are strongly urged to take immediate action to ensure that their NTP daemons are not susceptible to use in a distributed denial-of-service (DDoS) attack. Please also take this opportunity to defeat denial-of-service attacks by implementing ingress and Egress filtering through BCP38. See WindowsTimeServiceDev for discussion of this topic.
The final two security bugs reported by Google's Security Team have been fixed as of ntp-4.2.8p1.
A new set of mode 6 vulnerabilities has been discovered and, while these vulnerabilities can be reduced by making sure you have
restrict default … noquery in your
ntp.conf file, the best and most complete way to avoid these vulnerabilities is to install and deploy
ntp-4.2.8p1 which was released on 04 February 2015.
Are you using Autokey in production? If so, please contact Harlan - he's got some questions for you.
13.5. Windows Time Service
Beginning with Windows 2000, Microsoft includes the Windows Time Service with all versions of Windows. Initially, the pupose of Windows Time Service was to keep all clocks on the Windows network loosely synchronized to support Kerberos authentication, which is time-sensitive to a degree. Windows Time Service is also known as "w32time", and can be configured with the registry, Group Policy editor GUI tool, or the command-line tool w32tm.
Windows domain controller machines that are part of an Active Directory domain are automatically configured to act as time servers. The domain controller who is the Primary Domain Controller Emulator in the network is automatically configured to poll time.windows.com as a time source, and all subsequent domain controllors automatically obtain time from the Primary Domain Controller Emulator.
Windows domain member servers and domain member clients are automatically configured to receive time from domain controllers on the same network.
Stand-alone Windows servers and clients are automatically configured to poll
at one-hour intervals. The
server (actually a cluster of servers) is maintained by Microsoft. However,
is notoriously unreliable and heavily loaded, so configuring a different time source or multiple sources is probably wise.
An example configuration, suitable for a Windows 2003 standalone server or Primary Domain Controller Emulator in a Active Directory domain:
C:\>w32tm /config /update /manualpeerlist:"0.pool.ntp.org,0x8 1.pool.ntp.org,0x8 2.pool.ntp.org,0x8 3.pool.ntp.org,0x8" /syncfromflags:MANUAL
The above configuration tells Windows Time Service to use four servers from the NTP Pool, and use a client-mode association (identified by the
after each server name) to contact them. This configuration is analgous to
directives in the configuration file for
. Note that this configuration should not be used on Windows servers or clients that are members of an Active Directory domain, unless you absolutely want them to ignore time from Active Directory domain controllers on the network.
A second example, suitable for a laptop computer that is a member of a Windows Active Directory domain:
C:\>w32tm /config /update /manualpeerlist:"pool.ntp.org,0x8" /syncfromflags:MANUAL,DOMHIER
The above configuration tells Windows Time Service to both Active Directory domain controllers and
as time sources, so that domain controllers are used as time sources when the laptop is on the netowork, but pool.ntp.org is used when the machine is "on the road" but still connected to the Internet (at a WiFi hot-spot in your local coffee house, for example).
For detailed information, please see the Windows Time Service Technical Reference
The implementations in Windows 2000 and Windows XP are SNTP clients only, and not suitable for use as a server, although Windows 2000 domain conrollers incorrectly serve time at stratum 2 always, regardless of their time source configuration. This is a violation of the SNTP RFC, which states that SNTP systems can only act as servers if they have a local reference clock attached.
More recent versions, such as those in Windows 2003, Vista, and Windows 2008 are documented by Microsoft to be compliant implementations of the NTPv3 RFC 1305
Windows Time Service servers report a precision of -6, and do not appear to interpolate time between system clock ticks. This limits their absolute accuracy to ±16 ms, far below that of the reference ntpd implementaion. However, this accuracy is suitable for many networks and applications.
Reference clock support for the Windows Time Service is possible with third-party drivers. At this time, such drivers are essentially non-existent, meaning Windows Time Service can only act as a time server at Stratum 2 or below.