Re: [chrony-dev] Diagnosing pre-shared key authentication failure |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] Diagnosing pre-shared key authentication failure
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Mon, 17 Oct 2022 09:02:40 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1665990163; 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=ISgwI5yl0+F/A8A4o9szWQEVsz4PEjCiVQTeKosn5jo=; b=c43b3NPC+LaYnEsM21B+ffJXCVvkSTnQ1iZfNdRjsJbY9uZdp9qqLD5f+1bY4eX7HdcYc4 1Hnr2PdsrZe1huOKxCC4Aw+xJaTh4Yw6jeizsivs7XV3AfSrlO3OZb7RdpiB8pJDg/jHPe ILqsP3vguBvETDhrnQNYn5k35IqnTWo=
On Fri, Oct 14, 2022 at 12:58:16PM +0300, Avamander wrote:
> So when someone tries to MITM all NTS and (authenticated) NTP connections,
> they'd be marked unreachable just like the ones that are actually
> unreachable.
>
> Would it not benefit from a separate synchronization/selection status?
If you can make it reliable, sure. If it's just guessing, I'd rather
let the user/admin decide from the raw numbers. If there is missing
some statistic, we can add it.
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.