Udo van den Heuvel via devel writes:
> Ah, thanks, then I find:
>
> NTSc: certificate invalid: 10=>certificate has expired
How about you post the log for the whole key exchange and not always
just a single line and the another one in the next mail? Here's what
that looks like here:
2020-02-23T07
> NTSc: certificate invalid: 10=>certificate has expired
> is that a local expiration or a remote one?
That's your client side saying that it thinks the remote certificate has
expired. You could get the same error if your system clock was set into the
far future.
The local certificate (if a
On 23-02-2020 11:30, Achim Gratz via devel wrote:
> Udo van den Heuvel via devel writes:
>> ntpd[2256]: NTSc: NTS-KE req to pi4.rellim.com took 0.370 sec, fail
>
> You'd need the /^NTSc: / lines immediately preceding this to figure out
> where it failed. There is no full separation of all the dif
Udo van den Heuvel via devel writes:
> ntpd[2256]: NTSc: NTS-KE req to pi4.rellim.com took 0.370 sec, fail
You'd need the /^NTSc: / lines immediately preceding this to figure out
where it failed. There is no full separation of all the different fail
modes however, for instance a failed certificat
Hello,
What does a line of
ntpd[2256]: NTSc: NTS-KE req to pi4.rellim.com took 0.370 sec, fail
signify?
A remote issue?
Or a local failure?
What is failing exactly?
Kind regards,
Udo
___
devel mailing list
devel@ntpsec.org
http://lists.ntpsec.org/mai