| Re: Fwd: [chrony-users] ntp symmetric auth for internal clients |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: Fwd: [chrony-users] ntp symmetric auth for internal clients
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 2 Sep 2024 14:41:56 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1725280921; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=4uS0hI2XO70LvOF8BapwxDw6AOw5B9JrKxb0jxFWpmw=; b=bBhzf1a/y7+puyQDs8/rT7m094RdjIgvZ2XE7MAhkFabb3tp1ScNpAsIy3h4vqOLlhoSu4 8U77R0p4RRfYHGIHnsdI2Dj89zqPbOYw/Z2OUsq9qzmsRJWe12EjTznvMQU1rOeFkwXjX4 3lDiRlsQz1lkuYSxaV+EGCTIGGTkNr0=
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
--
Miroslav Lichvar
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.