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-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.
