Hal Murray :
> > I'll do a bug-triage pass.
>
> I've seen a couple of changes go by. Thanks.
>
> Please let me/us know when you are finished so I can test things.
Will do.
--
http://www.catb.org/~esr/;>Eric S. Raymond
___
devel
> I'll do a bug-triage pass.
I've seen a couple of changes go by. Thanks.
Please let me/us know when you are finished so I can test things.
--
These are my opinions. I hate spam.
___
devel mailing list
devel@ntpsec.org
Hal Murray via devel :
> > Has there been enough user visible improvement to warrent a release of
> > 1.1.10?
>
> I think so.
>
> 1.1.9 doesn't know about the new port number for NTS-KE.
>
> There is also a bug fix for a missing error message. Without that message,
> it's really tough to
> Has there been enough user visible improvement to warrent a release of 1.1.10?
I think so.
1.1.9 doesn't know about the new port number for NTS-KE.
There is also a bug fix for a missing error message. Without that message,
it's really tough to debug an obscure case of certificates not
HI,
I've been waiting as well on the RFC for 1.2
Has there been enough user visible improvement to warrent a release of 1.1.10?
..m
..ѥѸђ
Mark Atwood
Project Manager of the NTPsec Project
+1-206-604-2198
On Sat, Aug 29, 2020, at 11:58, Hal Murray wrote:
>
> The RFC isn't out yet and I
The RFC isn't out yet and I have no idea when it will get published.
I'd like to get an official release out that uses port 4460.
The current code still listens on port 123 as well as 4460. I'd like to
remove that when the RFC comes out and we release 1.2
--
These are my opinions. I
