r37 - 2015-05-14 - 08:37:54 - HarlanStennYou are here: NTP >  Main Web > SoftwareDevelopment
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.8p12 was released on 14 August 2018. It addresses 1 low-/medium-severity security issue in ntpd, 1 low-severity security issue in ntpq and ntpdc, and provides 27 non-security bugfixes and 4 other improvements over 4.2.8p11.

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.

NTP Software Development

New users should consult the documentation page before contacting the NTP development team with questions.


Tracking of NTP development concerns is done using Bugzilla, an open-source bug tracking system developed by the the Mozilla team. Our Bugzilla server is located at bugs.ntp.org. All users need a unique Bugzilla account, which can be created from the Bugzilla page. Users are encouraged to report bugs or suggest enhancements.

Source releases and patches

The development tarballs available in the HTTP archive are sometimes not suitable for production work, but the dev team produces development tarballs to provide users with specific needs the ability to get semi-stable software with important, new features that may not be available in the stable tree.

download Tarballs (for both the current release and development versions) are available from the software downloads page. Patch files, and other tarballs, are available in the HTTP archive.

BitKeeper Repositories

The NTP source is maintained in a BitKeeper repository.

For some history on this decision please see WhyBitKeeper.

Please note that if you are behind a firewall then you will need to open port 14690/TCP in order to use the bk://whatever URLs. (Is this still true? It may be that ssh is all that is required now...)

If you do not wish to use bk directly and you still want to access our repositories, you have two additional choices. You can browse the repositories and see the files and the metadata by visiting http://bk.ntp.org . If you want to download a repository, you may use rsync to get it.

Use the command rsync archive.ntp.org:: to see the list of rsync targets.

Please consult the rsync man-page, either your local copy or the on-line copy at http://www.samba.org/ftp/rsync/rsync.html, or the documentation at http://rsync.samba.org/ to find out how to use rsync.

Tools Needed to build from a BitKeeper repository

You must have the following tools to use the BitKeeper repository version of NTP:

  • autoconf - Version 2.61 or later. We use the latest version.
  • automake - Version 1.11 or later. We use the latest version.
  • libtool - Version 1.5.something (this is a guess - we use something recent).
  • lynx - Any version. We use this to generate the COPYRIGHT file.

The following tool is optional:

The following tools are only needed if you are planning to hack on the .def files which produce our command-line parsing and our generated documentation. Almost nobody will ever need these:

  • autogen - Version 5.18.5 or later. We use the latest version.
  • guile - needed by autogen.

Using the commercial BitKeeper client

The NTP Public Services Project is using the commercially licensed BitKeeper product. Project Committers may use this software for their project-related efforts, if they so choose; instructions for this are available at Info:GettingBk .

Once you have installed BitKeeper, you can clone the NTP repositories using the following commands:

For the ntp-stable repository, to ./ntp-stable:

   bk clone bk://bk.ntp.org/ntp-stable ntp-stable

For the ntp-dev repository, to ./ntp-dev:

   bk clone bk://bk.ntp.org/ntp-dev ntp-dev

Once you have obtained the sources, do the following, using REPO as the directory the repository was downloaded to (e.g.=./ntp-stable= or ./ntp-dev ):

   cd REPO
   ./bootstrap (To generate configure and Makefile.ins)

and you should be ready to go.

You can keep your repository up to date by running:

   cd REPO
   bk pull -v

For help on a BitKeeper (bk) command (e.g. clone), use bk clone --help.

Edit | WYSIWYG | Attach | Printable | Raw View | Backlinks: Web, All Webs | History: r41 | r39 < r38 < r37 < r36 | 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