All posts by NTPsec Project Blog

Remembering Doctor Mills

Post Syndicated from NTPsec Project Blog original https://blog.ntpsec.org/2024/01/21/remembering-mills.html

Remembering Dr Dave Mills

We were sad to learn that the creator of the NTP protocol, Dr David
L. Mills PhD has passed away.

Dr Mills designed the NTP distributed algorithm, while also writing
and maintaining the reference implementation on the very first
experimental inter-networking packet switches that were the creation
of the internet.

In that work he was supported by the other founders of the internet,
and by skilled developers and maintainers who assisted him, and by a
growing collection of skilled developers and maintainers who continued
maintaining the work that he started. The maintainers of the NTPsec
project count ourselves lucky to be amoung the people who followed in
his work.

The more we discovered reading the sources of his NTP implemention,
the more we became aware of his insight, technical ability, and his
hope and his dream that this little “inter-network experiment” could
grow to be literally world spanning. He was right, we we all owe him
much.

Thank you, Dr, Mills. The clocks of the world tick together in time
in large part due to you.

Version 1.2.3

Post Syndicated from NTPsec Project Blog original https://blog.ntpsec.org/2023/12/31/version-1.2.3.html

The NTPsec Project is pleased to announce the tagging of version 1.2.3

  • Change mode6 alignment to four, which may
    break some compatibility with classic NTP.

  • Seccomp should now also yield invalid syscall names when dying.

  • Make ntpq stop dropping output timestamp leading zeroes.

  • Update documents in quite a few places.

  • Reset some stats hourly, even when not logged into files.

  • Add error logging, and stats for ms-sntp.

  • Add spacing between multiple peer views in ntpq.

  • We think we have fixed ms-sntp but we can’t test it.
    If you can test it, please let us know if it does/doesn’t work.

  • ntpd and ntpq both treat SHA-1 as an alias for SHA1
    NIST uses SHA-1. The crypto package from OpenSSL uses SHA1.

  • The default crypto type for ntpq is now AES.
    RFC 8573 deprecated MD5.

  • There are now log files with hourly statistics for NTS and
    NTS-KE traffic: filegen ntsstats and filegen ntskestats,

  • Update ntpsnmpd to use python built-in to get uname information. NTPsec/ntpsec#791

  • Update license file names for REUSE compliance.

  • Fix ntploggps issue where count_used_satellites checked before it is initialized.

  • Print out OpenSSL version at configure time.

  • Enable debug symbols by default, with only an option to disable.

  • Add support for ecdhcurves list.

  • Fix build on platforms where -fstack-protector relies on libssp, like musl.

  • Fix ntpdig crash when using 2.ntp.pool.org with a host without IPv6 support.

  • Do not install libaes_siv test anymore.

  • Add update option to buildprep.

  • ntpdig shows packet delay in JSON output.

For other changes since the previous release, please consult
the project NEWS.adoc file
at https://gitlab.com/NTPsec/ntpsec/-/blob/master/NEWS.adoc

Getting this release

You can clone the git repo
from https://gitlab.com/NTPsec/ntpsec.git
and you can download the release tarballs with sums and signatures
from https://ftp.ntpsec.org/pub/releases/

This release is signed with the GPG key id
E57235D22764129FA4F2F4D17F52608ED0E49D76

Version 1.2.2a

Post Syndicated from NTPsec Project Blog original https://blog.ntpsec.org/2023/08/03/version-1.2.2a.html

The NTPsec Project is pleased to announce the tagging of version 1.2.2a

  • Fix a crash in ntpd if NTS is disabled and an NTS-enabled client request
    (mode 3) is received.
    (CVE-2023-4012)
    #794

For other changes since the previous release, please consult
the project NEWS.adoc file
at https://gitlab.com/NTPsec/ntpsec/-/blob/master/NEWS.adoc

Getting this release

You can clone the git repo
from https://gitlab.com/NTPsec/ntpsec.git
and you can download the release tarballs with sums and signatures
from https://ftp.ntpsec.org/pub/releases/

This release is signed with the GPG key id
E57235D22764129FA4F2F4D17F52608ED0E49D76

Version 1.2.2

Post Syndicated from NTPsec Project Blog original https://blog.ntpsec.org/2022/12/29/version-1.2.2.html

The NTPsec Project is pleased to announce the tagging of version 1.2.2

  • Restore/cleanup NTPv1 support

    • ntpq sysstats now shows NTPv1 traffic.

    • NTPv1 counter added to sysstats log file.

  • NTS supports partial wildcards, for example *.example.com

  • Work on documentation, ntpdate, ntpheat, ntploggpg, ntpq’s sysstats, ntpviz,
    and seccomp.

  • NTP auth no longer breaks on NULs.

  • The NTS server now saves 10 days worth of cookie keys. This will allow clients
    that only poll once a day to use NTS without using NTS-KE to keep cookies up to
    date.

  • rawstats now logs dropped packets and their BOGON code

    • Only one per request to avoid DoSing the log file

    • This lets you see packets that take too long.

  • Add 4 or 6 to DNS/NTS RefID tags to indicate that the
    DNS or NTS-KE has succeeded but NTP has not worked yet.

  • Build improvements

    • Respect --notests configure option for build

    • Add --enable-attic (default off)

    • Restore Python 2.6 support

    • Restore LibreSSL support

    • Add support for OpenSSL 3.0

  • Fix hash validation in ntpleapfetch again.

  • FreeBSD now gets nanosecond resolution on receive time stamps.

For other changes since the previous release, please consult
the project NEWS.adoc file
at https://gitlab.com/NTPsec/ntpsec/-/blob/master/NEWS.adoc

Getting this release

You can clone the git repo
from https://gitlab.com/NTPsec/ntpsec.git
and you can download the release tarballs with sums and signatures
from https://ftp.ntpsec.org/pub/releases/

This release is signed with the GPG key id
E57235D22764129FA4F2F4D17F52608ED0E49D76

Version 1.2.1

Post Syndicated from NTPsec Project Blog original https://blog.ntpsec.org/2021/06/07/version-1.2.1.html

version 1.2.1

The NTPsec Project is pleased to announce the tagging of version 1.2.1

Update ntpkeygen/keygone to properly filter # characters. (CVE-2021-22212)

Add dextral peers mode in ntpq and ntpmon.

Drop NTPv1 as the support was not RFC compliant, maybe v2 except mode 6 next.

Fix argument P for ntpd parsing fixed and ntpdate improvements.

Fix crash for raw ntpq readvar.

Add processor usage to NTS-KE logging except on NetBSD.

Remove –build-epoch and replace it with arbitrary –build-desc text.
Passing ‘–build-desc=$(date -u +%Y-%m-%dT%H:%M:%Sz)’ restores the previous
default extended version.

The build epoch has been replaced with a hardcoded timestamp which will be
manually updated every nine years or so (approx 512w). This makes the
binaries reproducible by default.

Compare versions of ntp.ntpc and libntpc printing a warning if
mismatched. Fix libntpc install path if using it.

Reduce maxclocks default to 5 to reduce the NTP pool load.

Print LIBDIR during ./waf configure.

Add documentation, new GPG key, and other cleanups.

For other changes since the previous release, please consult
the project NEWS.adoc file
at https://gitlab.com/NTPsec/ntpsec/-/blob/master/NEWS.adoc

Getting this release

You can clone the git repo
from https://gitlab.com/NTPsec/ntpsec.git
and you can download the release tarballs with sums and signatures
from ftp://ftp.ntpsec.org/pub/releases/

This release is signed with the GPG key id
E57235D22764129FA4F2F4D17F52608ED0E49D76

Version 1.2.0

Post Syndicated from NTPsec Project Blog original https://blog.ntpsec.org/2020/10/06/version-1.2.0.html

version 1.2.0

The NTPsec Project is pleased to announce the tagging of version 1.2.0

The minor version bump is to indicate official official support of
RFC8915 “Network Time Security for the Network Time Protocol” which
was released 2020-09-30.

For other changes since the previous release, please consult
the project NEWS.adoc file
at https://gitlab.com/NTPsec/ntpsec/-/blob/master/NEWS.adoc

Getting this release

You can clone the git repo
from https://gitlab.com/NTPsec/ntpsec.git
and you can download the release tarballs with sums and signatures
from ftp://ftp.ntpsec.org/pub/releases/

This release is signed with the GPG key id
E57235D22764129FA4F2F4D17F52608ED0E49D76
which is a new key.

About today

On this day in 1783, Benjamin Hanks received a patent for a
self-winding clock he planned to install in the Old Dutch Church in
Kingston, New York, supposedly making it the first public clock in
what became the New York City metropolitan area.

Version 1.1.9

Post Syndicated from NTPsec Project Blog original https://blog.ntpsec.org/2020/05/23/version-1.1.9.html

version 1.1.9

The NTPsec Project is pleased to announce the tagging of version 1.1.9

This should be the last point release of NTPsec before the Network
Time Security RFC is approved by the IETF. We expect to release 1.2.0
when that happens.

Analysis shows that CVE-2020-11868, affecting NTP Classic, cannot
affect us, as the peer mode involved has been removed.

For other changes since the previous release, please consult
the project NEWS.adoc file
at https://gitlab.com/NTPsec/ntpsec/-/blob/master/NEWS.adoc

Getting this release

You can clone the git repo
from https://gitlab.com/NTPsec/ntpsec.git
and you can download the release tarballs with sums and signatures
from ftp://ftp.ntpsec.org/pub/releases/

This release is signed with the GPG key id
B48237761A2690222C995F445A22E330161C3978

About today

Today is Blursday, Maprilay 84th, 2020, of the COVID-19 panic.

On this day, in 1844, the first commerical telegraph line came online.

Copyright statements do not need the year

Post Syndicated from NTPsec Project Blog original https://blog.ntpsec.org/2020/02/15/copyright-year.html

I need to preface this post with the statement that I am not a lawyer,
and that I am not speaking on behalf of my dayjob employer.

There is no need to include the year in a copyright declaration
statement.
And related, there is no need to update the year
statement, add new year statements, manage year range statements, or
any of that stuff. It is tedious, boring, adds no value, and prevents
no risks.

Several large legally sophisticated companies, include Amazon, Google,
Microsoft, and Facebook, are now publishing open source code with
copyright statements without a year.

And so, I have added the following to our devel/hacking document.

Do not specify a year in a copyright statement. Most of the existing
copyright statements already present in the project have been scrubbed
of the year. There is no need to specify the year in a copyright
statement. Several large legally sophisticated companies, include
Amazon, Google, Microsoft, and Facebook, are now publishing open
source code with copyright statements without a year. We encourage
the larger open source community to emulate this.

Being able to do this now has taken a surprisingly large amount of
work behind the scenes, especially on the part of those large
companies. Do please take advantage of it, and write simpler
copyright statements in your open source projects from now on.

Version 1.1.8

Post Syndicated from NTPsec Project Blog original https://blog.ntpsec.org/2019/11/17/version-1.1.8.html

version 1.1.8

The NTPsec Project is pleased to announce the tagging of version 1.1.8

As aways, the most accurate record of changes is in the
NEWS file, the git log, and the git history.

This version has fixes and tweaks to handling certs for NTS.

We have also removed the last #define _XOPEN_SOURCE, as well as
removing many other now unneeded #ifdefs, and cleaned up warnings
and build issues for several OS targets. See the git history for details.

Getting this release

You can clone the git repo
from https://gitlab.com/NTPsec/ntpsec.git
and you can download the release tarballs with sums and signatures
from ftp://ftp.ntpsec.org/pub/releases/

This release is signed with the GPG key id
B48237761A2690222C995F445A22E330161C3978

Commento and Gitlab

Post Syndicated from NTPsec Project Blog original https://blog.ntpsec.org/2019/09/04/commento-gitlab.html

Commento and Gitlab

Last December, I switched the comment processor for this blog from
Disqus to Commento, and discussed by reasons in
the blog post
Switch from Disqus to Commento.
Mainly it was because we didn’t like the adtech tracking and the injected
adverts.

We’ve been happy with it since the switch, it’s Just Worked.

My only complaint when we switched to it was the only social login it
supported was with Google. Well, that’s been fixed, and has added
social login from some other big sites, including Gitlab. Just what
we wanted!

If do find any problems with Commento, let them know. If you are
using Disqus on any of your own sites, consider
Commento instead.

Version 1.1.7

Post Syndicated from NTPsec Project Blog original https://blog.ntpsec.org/2019/09/02/version-1.1.7.html

version 1.1.7

The NTPsec Project is pleased to announce the tagging of version 1.1.7

As aways, the most accurate record of changes is in the
NEWS file, the git log, and the git history.

The numeric literal argument of the ‘time1’ fudge option on a clock
can now have one or more letter suffixes that compensate for era
rollover in a GPS device. Each “g” adds the number of seconds in a
1024-week (10-bit) GPS era. Each “G” adds the number of seconds in a
8192-week (13-bit) GPS era.

The neoclock4x driver has been removed, due to the hardware and the
vendor having utterly vanished from the face of the earth.

The NTS ALPN negotiation sequence has been modified for improved
interoperability with other NTS implementations.

NTS key rotation now happens every 24 hours. It used to rotate
every hour to enable testing of recovery from stale cookies.

Getting this release

You can clone the git repo
from https://gitlab.com/NTPsec/ntpsec.git
and you can download the release tarballs with sums and signatures
from ftp://ftp.ntpsec.org/pub/releases/

This release is signed with the GPG key id
B48237761A2690222C995F445A22E330161C3978

Version 1.1.6

Post Syndicated from NTPsec Project Blog original https://blog.ntpsec.org/2019/07/10/version-1.1.6.html

version 1.1.6

The NTPsec Project is pleased to announce the tagging of version 1.1.6

We have been shipping weekly because of ongoing development of NTS.

As aways, read the …​/NEWS file, and the git log and git history.

Getting this release

You can clone the git repo
from https://gitlab.com/NTPsec/ntpsec.git
and you can download the release tarballs with sums and signatures
from ftp://ftp.ntpsec.org/pub/releases/

This release is signed with the GPG key id 0x5A22E330161C3978.

Version 1.1.5

Post Syndicated from NTPsec Project Blog original https://blog.ntpsec.org/2019/06/30/version-1.1.5.html

version 1.1.5

The NTPsec Project is pleased to announce the tagging of version 1.1.5

News

We do not normally ship a release only one week after the previous,
however it is HIGHLY RECOMMENDED that if you are using NTS you
upgrade to this version.

We have added ALPN to be consistent with the NTS draft. And we have
discovered and fixed a buffer overrun in debug compile of ALPN
implementation. If you are running NTPsec 1.1.4 with NTS turned on
and with with the compile time debug flags turned on, it is possible
for an attacker to send a packet that will crash your server.

As aways, read the …​/NEWS file, and the git log and git history.

Today

On this day in 1972 the first leap second is added to the UTC time system.

Getting this release

As always,
you can clone the git repo
from https://gitlab.com/NTPsec/ntpsec.git
and you can download the release tarballs with sums and signatures
from ftp://ftp.ntpsec.org/pub/releases/

This release is signed with the GPG key id 0x5A22E330161C3978.