Mind running the timings with the legacy interfaces as well? We may determine that the speed benefits are outweighed by the risks and complexities of an older API, but it would be good to have the data so we can make an informed decision.
https://www.openssl.org/docs/man1.0.2/crypto/md5.html https://www.openssl.org/docs/man1.0.2/crypto/sha.html Greg On Sun, Jan 29, 2017 at 7:50 AM Eric S. Raymond <e...@thyrsus.com> wrote: > Hal Murray <hmur...@megapathdsl.net>: > > The speedup applies to any type of crypto. I didn't bother implementing > the > > MD5 half. The change is just cleaning up the per-digest initialization. > > We'll want it for anything going forward. > > Please commit it, then. And please do the MD5 code in > libntp/a_md5encrypt.c > and libntp/ssl_init.c to; might as well fix it all at once. > -- > <a href="http://www.catb.org/~esr/";>Eric S. Raymond</a> > _______________________________________________ > devel mailing list > devel@ntpsec.org > http://lists.ntpsec.org/mailman/listinfo/devel >
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
