Re: NTP to Chrony migration issue with NTP authentication with symmetric keys
Miroslav Lichvar <[email protected]>
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <ZUijMEyTugx3DMu7@localhost> |
On Fri, Nov 03, 2023 at 02:35:21PM -0500, Michael Krell wrote: > I'm raising this issue because, with that same Chrony configuration on > our product, we actually have another test passing - we have stood up a > separate Chrony server with the same key and Chrony configuration and it > can sync time via the symmetric key authentication just fine. The problem > we're having is with backwards compatibility to NTP itself. Since we are > mandated to be backwards compatible with NTP, we would like to see if this > is something new. The issue likely is in the key specification (ASCII vs HEX) or truncated vs untruncated digest with length over 160 bits, which requires "version 4" in the chrony config as explained in the man page. Please post sample configs and key files for both ntpd and chrony. -- Miroslav Lichvar -- To unsubscribe email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "unsubscribe" in the subject. For help email chrony-users-request-kWFZVVI9zxvPqho9SqqRMmD2FQJk+8+b@public.gmane.org with "help" in the subject. Trouble? Email [email protected]