[158121] in North American Network Operators' Group
RE: NTP Issues Today
daemon@ATHENA.MIT.EDU (Chuck Church)
Wed Nov 21 08:28:34 2012
From: "Chuck Church" <chuckchurch@gmail.com>
To: "'Jimmy Hess'" <mysidia@gmail.com>
In-Reply-To: <CAAAwwbWP_QP08u3xmku4tqU9rg3XsuaHqJdt3PYiZHH02O5SFA@mail.gmail.com>
Date: Wed, 21 Nov 2012 08:28:06 -0500
Cc: nanog@nanog.org
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
-----Original Message-----
>From: Jimmy Hess [mailto:mysidia@gmail.com]
>Sent: Tuesday, November 20, 2012 7:50 PM
>To: Van Wolfe
>Cc: nanog@nanog.org
>Subject: Re: NTP Issues Today
>This _should_ have caused NTP to execute a panic shutdown,
>instead of setting the clock back 30 million seconds.
>--
>-JH
Sounds like SNTP might have been on the client. Doesn't do much if any
sanity checking. Windows used to use that, was more than happy to change
the time by years if bad time received. Not sure if that is still the case.
Chuck
