> I think that our implementing this is a good reason for make a point release.
Sounds good. I'll have code ready in a day or 3.
What else should we be working on or testing? (I need to update the doc on
rate limiting.)
--
These are my opinions. I hate spam.
I think that our implementing this is a good reason for make a point release.
..ѥѸђ
Mark Atwood
Project Manager of the NTPsec Project
+1-206-604-2198
On Mon, Mar 23, 2020, at 01:24, Hal Murray wrote:
>
> A new version of the draft RFC is available:
>
On 3/23/20 5:43 AM, Eric S. Raymond via devel wrote:
> Hal Murray :
>> We can do several things:
>> 1) clean out the ifdefs that make things work with older versions of
>> OpenSSL.
>> That is drop support for systems that haven't upgraded their OpenSSL to
>> a
>> supported version.
>>
Hal Murray :
> We can do several things:
> 1) clean out the ifdefs that make things work with older versions of
> OpenSSL.
> That is drop support for systems that haven't upgraded their OpenSSL to a
> supported version.
> 2) leave things alone, ignore the RFC.
> Or maybe add some
A new version of the draft RFC is available:
https://datatracker.ietf.org/doc/draft-ietf-ntp-using-nts-for-ntp/
They decided to drop support for TLS 1.2. Details way down.
They also tweaked the TLS export string used to make client-server keys. That
will break things if the client and
