Re: Fwd: ntp symmetric auth for internal clients

Am 02.09.24 um 14:41 schrieb Miroslav Lichvar:
> On Mon, Sep 02, 2024 at 02:31:03PM +0200, Ede Wolf wrote:
>> As for specifying the key on the client side, that is exactly what I have
>> done, still ntpd claims auth = bad
>>
>> The issue seemd to be sha1, as using a md5 key, something I have avoided so
>> far, makes everything work.
> 
> It might be an issue with ntpd using different keys than what you
> expect. ntpd interprets shorter keys as ASCII and longer as HEX. With
> chrony you have to tell what it is.
> 
> If unsure, try this conversion script:
> https://github.com/mlichvar/ntp2chrony
> 

Again, thanks very much for your time and help. chronyc keygen showed 
the proper syntax as well. As you mentioned, defining the type worked, 
so simply adding HEX: before the sha1 key (and removing the comments at 
the end) made everything work with sha1 keys again.


-- 
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]