[189245] in North American Network Operators' Group
Re: NIST NTP servers
daemon@ATHENA.MIT.EDU (Jared Mauch)
Thu May 12 10:34:36 2016
X-Original-To: nanog@nanog.org
From: Jared Mauch <jared@puck.nether.net>
In-Reply-To: <20160511174254.GB19142@puck.nether.net>
Date: Thu, 12 May 2016 10:34:31 -0400
To: Majdi Abbas <msa@latt.net>
Cc: North American Network Operators' Group <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
> On May 11, 2016, at 1:42 PM, Majdi S. Abbas <msa@latt.net> wrote:
>=20
> On Wed, May 11, 2016 at 03:24:43PM +0000, Jay R. Ashworth wrote:
>> We're all aware this project is underway, right?
>>=20
>> https://www.ntpsec.org/
>=20
> Despite the name, I'm not aware of any significant protocol
> changes. It's just a recent fork of the reference implementation
> minus the refclocks, which isn't particularly helpful if you /don't/
> trust network time sources.
I=E2=80=99ll also say that if you=E2=80=99re running NTP with -g beware.
"This option allows the time to be set to any value without =
restriction=E2=80=9D
Game over if someone decided to go after you, you will never sync. Make =
sure
systemd won=E2=80=99t just restart your daemon, if you get =E2=80=9Cinvali=
d=E2=80=9D time the process
dies and then you=E2=80=99re off. Game over, press redo or back. (yay =
ti99/4a references)
- Jared
