Re: Second key always fails

Miroslav Lichvar <[email protected]>
Newsgroups gmane.comp.time.chrony.user
Message-ID <YtgP8u3cNFJIHrld@localhost>
On Wed, Jul 20, 2022 at 02:16:11PM +0000, Gregor WALTZ wrote:
> Only the key labeled as 1 in the key file works. The line position in the file does not matter (just the label). If I use the same configuration but with a key labeled any number other than 1, chronyd fails.
> My server in the examples is ntpd 4.2.8p4 from ntp.org. I have the same results with 4.2.8p10.
> chronyd is version 4.2.

The server is responding with a crypto NAK. Does it have the same keys
in its keyfile, with the same numbers 1 and 2?

-- 
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]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.