time.cloudflare.com is now on port 4460

Hello, We're now listening on the official port. Let me know if there are any issues. Sincerely, Watson ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel

Re: thinking of tagging 1.2.0 for when NTS is officially official.

On Thu, Jun 4, 2020 at 7:11 AM Hal Murray via devel wrote: > > >> Step 1 will be to listen on both old and new port # > >> Step 2 is to switch the client side to default to the new port #. > >> Step 3 is to stop listening on the old port #. > >> Plan B is to merge them all 3 steps and tolera

Re: thinking of tagging 1.2.0 for when NTS is officially official.

On Sat, May 30, 2020 at 5:51 PM Hal Murray via devel wrote: > > > I'm thinking of tagging 1.2.0 for when NTS is officially official. > > Seems like a good plan. > > I'm expecting there will be a new port number assigned for the KE server. > Step 1 will be to listen on both old and new port # >

Re: Heads up: incompatible NTS change, Monday midnight, UTC

On Thu, May 7, 2020 at 4:31 PM Hal Murray via devel wrote: > > > devel@ntpsec.org said: > > I have upgraded to ntpd ntpsec-1.1.8+ (git rev 36bb89920) and I > > believe I'm seeing this problem. > > You aren't connecting to ntp1.glypnod.com either, so that's probably not a > cloudflare problem. > >

Re: Heads up: incompatible NTS change, Monday midnight, UTC

I've gotten reports from some users of a remaining incompatibility with time.cloudflare.com and the code currently in git. I'm going to dig into it, but let me know if you have other reports. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org

Re: cloudflare refers NTS users to wrong page

On Mon, Dec 9, 2019, 9:47 PM Hal Murray via devel wrote: > > > I also might have a local issue as I get: > > NTSc: certificate invalid: 20=>unable to get local issuer certificate > > (for the other servers mentioned at the howto page) > > What OS/distro/version are you using? > > Do you have the

Re: Next release

On Wed, Nov 20, 2019, 7:32 AM Hal Murray via devel wrote: > > The RFC for NTS should be out soon. I don't know when that will actually > happen, but I think we should try to be in a position to make any last > minute > changes, for example, the port number, and push the button for a wonderful >

Re: Problems with NTS support

Nah the extra steps were just because I hadn't done it before and had some ports that hadn't been updated in a while. It really is just install bison and python. On Fri, Jun 14, 2019, 8:44 PM Gary E. Miller via devel wrote: > Yo Watson! > > Can you just send us your .bash_history file? > > On Fr

Re: Problems with NTS support

: > > Yo Watson! > > On Fri, 14 Jun 2019 20:23:29 -0700 > Watson Ladd wrote: > > > On Fri, Jun 14, 2019 at 6:42 PM Gary E. Miller via devel > > wrote: > > > > > > Yo Watson! > > > > > > On Fri, 14 Jun 2019 18:23:03 -0700 > > &

Re: Problems with NTS support

On Fri, Jun 14, 2019 at 6:42 PM Gary E. Miller via devel wrote: > > Yo Watson! > > On Fri, 14 Jun 2019 18:23:03 -0700 > Watson Ladd via devel wrote: > > > It seems that to use NTS to authenticate a server one must also > > configure the local ntpd daemon to s

Problems with NTS support

Dear all, It seems that to use NTS to authenticate a server one must also configure the local ntpd daemon to serve NTS. This is a barrier to adoption: lots of systems take the time but don't set it. ntpdig doesnt seem to have NTS options, which prevents me from using it as a quick testing tool.