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.
Windows Porting Issues
NTP can be built under the following versions of Windows (please update as needed):
using the following toolchains (please update as needed)
- Visual Studio 2005
- Visual Studio 2008
- Visual Studio 2010 (work-in-progress)
The "Express Editions" of these are free. The C++ version will get you the C compilers we need.
As currently provided, you will need a version of OpenSSL installed:
(Please update with the appropriate versions of the above, and any extra needed packages.)
If you open the "ntp" project you'll see it is comprised of 9 projects.
For example, right-clicking on
will get you a menu, and in that menu right-clicking on "Properties" will get you a window that talks about a bunch of things, like Linker -> Input, where you'll see that we want to link with
There is a step-by-step recipe here: https://www.satsignal.eu/ntp/setup.html#build
Where does one set things like the
Instructions for setting environment variables are here: https://www.itechtalk.com/thread3595.html
On my own system, I have these two set to:
Just to be sure, this project builds a 32-bit NTP, right?
Yes, that's right. You can build either a Release or a Debug version.