r8 - 2006-08-06 - 05:52:23 - HarlanStennYou are here: NTP >  Support Web > StartingNTP
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.

ntp-4.2.8p2, released on 7 April 2015, addresses two issues with crafted packets involving symmetric key encryption and Message Authentication Codes.

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.
REFACTOR See StartingNTPDev for discussion of this topic.

7. Starting NTP

7.2. How is NTP started?

On Unix-like operating systems NTP is started by an init script. If you are installing a pre-packaged version of NTP, the init script infrastructure may be pre-configured for you. If you are installing directly from the source you may have to manually configure your init system to start NTP at boot time.

7.3. When should NTP be started?

NTP should be started early in the boot process: after the network and DNS (if you are using any names instead of IP addresses for your servers/peers) are configured, but before any time-sensitive services are started.

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