NTP Changelog

New in version 4.2.6p5

December 26th, 2011
  • This version updates sys_rootdisp and sys_jitter calculations to match the RFC specification, fixes a potential IPv6 address matching error for the "nic" and "interface" configuration directives, suppresses the creation of extraneous ephemeral associations for certain broadcastclient and multicastclient configurations, cleans up some ntpq display issues, and includes improvements to orphan mode, minor bugfixes, and code clean-ups.

New in version 4.2.6p3 (January 4th, 2011)

  • This version includes build infrastructure updates, code clean-ups, minor bugfixes, the resolution of a number of minor ref-clock issues, documentation revisions, and new features in ntpd, ntp-keygen, ntpsnmpd, and sntp.
  • Portability improvements in this release affect AIX, Atari FreeMiNT, FreeBSD4, Linux, and Microsoft Windows.

New in version 4.2.6p2 (July 10th, 2010)

  • [Bug 1581] size_t printf format string mismatches, IRIG string buffers undersized. Mostly backported from earlier ntp-dev fixes by J├╝rgen Perlinger.

New in version 4.2.6p1 (April 12th, 2010)

  • [Bug 1514] Typo in ntp_proto.c: fabs(foo < .4) should be fabs(foo) < .4.
  • [Bug 1464] synchronization source wrong for refclocks ARCRON_MSF (27) and SHM (28).
  • Correct Windows port's refclock_open() to return 0 on failure not -1.
  • Correct CHU, dumbclock, and WWVB drivers to check for 0 returned from refclock_open() on failure.
  • Correct "SIMUL=4 ./flock-build -1" to prioritize -1/--one.

New in version 4.2.5p210 (September 7th, 2009)

  • This is an automated development snapshot release.

New in version 4.2.5p208 (August 31st, 2009)

  • This is an automated development snapshot release.

New in version 4.2.5p207 (August 31st, 2009)

  • This is an automated development snapshot release.

New in version 4.2.4p6 (January 9th, 2009)

  • This release fixes oCERT.org's CVE-2009-0021, a vulnerability affecting the OpenSSL library relating to the incorrect checking of the return value of EVP_VerifyFinal function.
  • Credit for finding this issue goes to the Google Security Team for finding the original issue with OpenSSL, and to ocert.org for finding the problem in NTP and telling us about it. This is a recommended upgrade.