I haven't seen anyone mention this on the list, but found on the Debian
changelog for ntpsec:
ntpsec (1.2.3+dfsg1-1) unstable; urgency=low
[...]
- We think we have fixed ms-sntp
Thanks to Jakob Haufe for testing. (Closes: 1033088)
[...]
-- Richard Laager<rlaager at debian.org> Sun, 10 Mar 2024 22:01:29 -0500
This version is for Debian Trixie; currently, no mention of backporting
to Bookworm.
https://packages.debian.org/testing/ntpsec
Dale
Maybe Matching Threads
- Time synchronization problem. Chrony, ntp
- The care and feeding of the signing socket; also NTPsec
- The care and feeding of the signing socket; also NTPsec
- Time synchronization problem. Chrony, ntp
- The failure of that guy from NTPsec getting an RID / Key Identifier
Wisdom of the Ancients
