devel@ntpsec.org said:
> I see no real blockers. We've got a bunch of little nits and documentation
> issues. I might try to push a fix for #446.
There is no problem unless you setup your keys file to use an algorithm with
a big digest.
The short term clean fix is to reject algorithms with t
> Hal, is there anything I can do to help? I admit that it looks like the
> kind of thing we'd be better off letting you chew on than taking the time to
> fylly educate someone else, but if you don't think that's true I'm
> listening.
I just tried again.
It's not hard to explain. I'll try to
Hal Murray via devel :
> > Are we comfortable with the 1.0.1 release on March 3rd?
>
> I'm not. My attempts at fixing #461 aren't working.
>
> I think it should be simple. I think I understand what the problem is, but I
> don't understand why my attempts at fixing it aren't working.
>
> The r
Mark Atwood, Project Manager via devel :
> Are we comfortable with the 1.0.1 release on March 3rd?
>
> I look forward to seeing it move down all the distribution pipelines.
> Google Alerts have shown 1.0.0 in Debian, Ubuntu, and Gentoo distribution
> build reports.
I see no real blockers. We've
> Are we comfortable with the 1.0.1 release on March 3rd?
I'm not. My attempts at fixing #461 aren't working.
I think it should be simple. I think I understand what the problem is, but I
don't understand why my attempts at fixing it aren't working.
The root of the problem is this (from the ma
Are we comfortable with the 1.0.1 release on March 3rd?
I look forward to seeing it move down all the distribution pipelines.
Google Alerts have shown 1.0.0 in Debian, Ubuntu, and Gentoo distribution
build reports.
..m
On Tue, Feb 20, 2018 at 6:41 PM Mark Atwood wrote:
> Hi!
>
> A few months a
Gentlemen,
This was sent to "cont...@ntpsec.org", and I thought it should end
up to your attention.
- JDB
Forwarded Message
Subject:[cont...@ntpsec.org] draft-ietf-ntp-ma and
draft-ietf-ntp-using-nts-for-ntp in NTPSec?
Date: Tue, 27 Feb 2018 04:25:23 +
