ntpsec (1.2.5+dfsg-1) unstable; urgency=medium The long-standing bug where `pool` entries count towards `maxclock` has been fixed. The default ntp.conf has been updated accordingly. If you have customized your `ntp.conf`, you can reduce `tos maxclock` by the number of `pool` entries in the file to retain the previous number of pool servers. -- Richard Laager Sun, 23 Aug 2026 15:09:49 -0500 ntpsec (1.2.1+dfsg1-6) unstable; urgency=low ntpsec is replacing ntp in Debian. If you were already using ntpsec, you can stop reading now. For those coming from ntp, NTPsec is a drop-in replacement for common configurations, but some things have been removed or changed in the name of security and/or maintainability: https://docs.ntpsec.org/latest/ntpsec.html If you use a hardware clock, note that the Debian ntpsec package builds only the following drivers: arbiter,generic,hpgps,jjy,local,nmea,pps,shm,spectracom,trimble,zyfer NTPsec upstream dropped or deprecated several drivers: https://www.ntpsec.org/removal-plan.html https://www.ntpsec.org/drivers.html I am not building deprecated drivers. However, if the reason for a driver's deprecation is only "two digit years", I am building it. gpsd can be connected to ntpd using the SHM driver: # GPS PPS reference (NTP1) refclock shm unit 1 refid PPS # GPS Serial data reference (NTP0) refclock shm unit 0 refid GPS For more gpsd <-> ntpd configuration details, see: https://www.ntpsec.org/white-papers/stratum-1-microserver-howto/ https://gpsd.gitlab.io/gpsd/gpsd-time-service-howto.html The modem driver, despite working the last time I tested it, is NOT built because: 1. Modems are not very common any more. 2. Modem time services are disappearing (e.g. USNO's Washington D.C. number no longer answers). 3. The telephone network is increasingly packet-switched rather than circuit-switched. So you might as well use the Internet. 4. Internet connections are always on. 5. GPS receivers are cheap. -- Richard Laager Sun, 03 Apr 2022 15:23:36 -0500