Hash function support, MD5 / SHA256, strawman proposal

[Mark Atwood]

How stable is their ID?

How much effort will it be to add it to NTPsec?

My next strawman proposal that we add it NTPsec as soon as convenient, but
make it an option for now.

..m

On Fri, Jan 27, 2017 at 10:40 AM Mark Atwood <fallenpegasus at gmail.com>
wrote:

> Ok, thanks for the update.
>
> ..m
>
> On Fri, Jan 27, 2017 at 10:38 AM Daniel Franke <dfoxfranke at gmail.com>
> wrote:
>
> Sharon and Aanchal are already working on a better proposal and have
> an I-D for it. The new MAC function for legacy authentication
> ("legacy" as opposed to NTS) is going to be AES-CMAC.
>
> On 1/27/17, Mark Atwood <fallenpegasus at gmail.com> wrote:
> > How hard would the following be?
> >
> > Just go ahead and add SHA256 to NTPsec
> > then
> > Write an I-D modifying the NTP4 protocol documenting it.
> > then
> > Write a patch to NTP classic for it.  (yes, I know, icky code)
> >
> > ..m
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20170128/a4f62fcd/attachment.html>