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.
The NTP Project used no source code management for many years.
Eventually, we started using CVS, and that worked well for a while.
After a while, the limitations of CVS started driving Harlan crazy, and since he is the driver of the beast, he looked for a replacment. After about 2 more YEARS of study and looking, he chose BitKeeper and has been very happy with it ever since.
In early 2005, it was announced that BitMover would be stopping its free use license for BitKeeper.
While we are looking to continue on using the commercial version of BitKeeper, people have been asking about evaluating a replacement for BitKeeper.
The SCM must be invisible to Dave Mills
its use must not require any signature from anybody at UDel for its use there
it must support file and directory renames
it must support tracking of file/directory permission attribute changes
it should support checkins for work-in-progress
it must support the functionality we have with the existing triggers, described in the BitKeeper/triggers/trigger.cfg file of any ntp-dev or ntp-stable repo, which execute the following scripts:
If you would prefer to add your comment below instead of editing the table above, please do so. You can also email your comments to email@example.com .
One of the major gripes with P4 amoungst the FreeBSD userbase is the utter lack of decent support for anonymous r/o checkouts. In this respect, switching to perforce would make "public" access to ntp's development source much worse than it is now. -- TWikiGuest - 06 Dec 2005 15:27:22
Here's my first pass...
Please comment below or edit above, as appropriate.
-- HarlanStenn - 09 May 2005