r1 - 2011-03-05 - 03:13:33 - HarlanStennYou are here: NTP >  Main Web > SoftwareDevelopment > WhyBitKeeper
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.8p11 was released on 27 February 2018. It addresses 2 low-/medium-, 1 informational-/medium-, and 2 low-severity security issues in ntpd, 1 medium-severity security issue in ntpq, and provides over 65 non-security bugfixes and other improvements over 4.2.8p10.

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.

Why BitKeeper?

For many years, the NTP source code was kept in a frequently-backed-up directory on a machine. The only "snapshots" we had of previous releases were whatever tarballs we kept of previous releases. In early '99, Harlan and Dave came to an agreement about how a code repository would have to behave and Harlan was finally able to import the codebase into CVS (knowing full well what the limitations of CVS were).

In less than a year, the pains of using CVS were becoming unbearable, and the search began for a replacement. Over a period of 2 years' time, all opensource Source Code Management (SCM) Systems were explored and tested and several commercial solutions were examined (to various degrees) as well. Fairly quickly, it became obvious that BitMover's BitKeeper product was, hands-down and very clearly, the best SCM available for NTP. Its features included:

  • distributed (and disconnected) operation
  • integration areas
  • useful triggers/hooks
  • great merge capability
  • the ability to have multiple active repositories (eg, one repo per bugfix)
  • good performance
  • rock-solid stability
  • great support
  • quick, simple and easy to use
  • behaves well and, generally, "as expected"

Originally, the complete bk software/executable was available to anybody who wanted to use it to work on opensource projects. A series of events happened that resulted in increased restrictions on the ability of many opensource projects to continue to use BitKeeper. Harlan remains Very Pleased that NTP managed to stay clear of that situation, and believes the NTP Project has benefited greatly from its use of BitKeeper.

-- HarlanStenn - 2010-06-22

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r1 | 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-2018 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