Re: NTP to Chrony migration issue with NTP authentication with symmetric keys
Miroslav Lichvar <[email protected]>
| Newsgroups | gmane.comp.time.chrony.user |
|---|---|
| Message-ID | <ZUkH/vSQLOFt08Au@localhost> |
On Mon, Nov 06, 2023 at 09:00:18AM -0600, Michael Krell wrote: > Our implementation currently uses ASCII keys, and follows the 'optional' > usage for ASCII (Per the man page for chrony.conf : " The key can be > specified as a string of ASCII characters not containing white space with > an optional *ASCII:* prefix, or...". > /etc/chrony.keys : > > 20 SHA1 421b67770525bde2e926354a88ae2f81c7c76108 > /etc/ntp.keys: > > 20 SHA1 421b67770525bde2e926354a88ae2f81c7c76108 #RSA-SHA1-compliant This is not an ASCII key. ntpd interprets keys longer than 20 characters as hexadecimal values, so you need to add HEX: to the key in chrony.keys. -- 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]