[PATCH] ntpd: make NTP client Y2036-ready

[Kang-Che Sung]

On Monday, May 9, 2022, Miroslav Lichvar <mlichvar at redhat.com> wrote:
> The 32-bit integer part of the NTP timestamp overflows in year 2036,
> which starts the second NTP era.
>
> Modify the timestamp conversion to shift values between 1900-1970 (in
> the first era) to the second era to enable the client to synchronize
> correctly until year 2106 (assuming 64-bit time_t).
>
> Signed-off-by: Miroslav Lichvar <mlichvar at redhat.com>

Is this the right fix where there is no check on the era number?
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20220510/0bb438ee/attachment.html>