Current status of --enable-crypto

[Greg Rubin]

While I cannot speak specifically to NTP, SHA (without any suffix) has been
used on other contexts to mean SHA-1. I've also never encountered SHA-0
being used in any standard. So, if NTP is actually using it and it's not
just a misunderstanding, that would be a first for me. I suspect it is
SHA-1 throughout.

Greg

On Fri, Jan 27, 2017, 9:07 PM Eric S. Raymond <esr at thyrsus.com> wrote:

> Matthew Selsky <Matthew.Selsky at twosigma.com>:
> > Where do we get SHA-0, aka "sha", keytype support from if we remove the
> in-tree public domain version?
>
> To my knowledge the only SHA we have in tree is SHA-1.  I think you can
> only
> get SHA-0 via OpenSSL.
> --
>                 <a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
> _______________________________________________
> devel mailing list
> devel at ntpsec.org
> http://lists.ntpsec.org/mailman/listinfo/devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20170128/4e262a73/attachment.html>