Going in circles without a real-time clock
rachelbythebay.com
Going in circles without a real-time clock
1–10 of 157 posts
Re: Going in circles without a real-time clock
#2Re: Going in circles without a real-time clock
#3WireGuard only requires a monotonic clock, because it periodically rotates keys to provide the forward secrecy. Peer clocks are otherwise not required to be synchronized [1]. I guess the clock had a higher rate than usual and it couldn't be corrected due to the lack of RTC?
[1] https://www.wireguard.com/papers/wireguard.pdf#page=7 "In fact, it does not even have to be an accurate timestamp; it simply must be a per-peer monotonically increasing 96-bit number."
Re: Going in circles without a real-time clock
#4tl;dr: machine is unable synchronize its clock because it won't trust the NTP server's DNSSEC certificate because its clock isn't synchronized. Oof.
Re: Going in circles without a real-time clock
#5Re: Going in circles without a real-time clock
#6What is she referring to by “THE ONE”?
Re: Going in circles without a real-time clock
#7tl;dr: machine is unable synchronize its clock because it won't trust the NTP server's DNSSEC certificate because its clock isn't synchronized. Oof.
While systemd-timesyncd contains a workaround for this, chrony does not seem to.
Re: Going in circles without a real-time clock
#8Re: Going in circles without a real-time clock
#9What is she referring to by “THE ONE”?
Re: Going in circles without a real-time clock
#10What is she referring to by “THE ONE”?