Update

[Eric S. Raymond]

Hal Murray via devel <devel at ntpsec.org>:
> It seems strange to use "crypto" for the keyword when we are talking about NTS 
> or NTS-KE.

Yes, I was planning to change that.  I originally thought there were going to be
crypto options that might someday be be used for something besides NTS and
intended to have bith "crypto" and "nts" commands, but that is multiplying
entities beyond necessity. 

I'll fix it later today.

> The documentation for crypto enable says:
>   Enable NTS service. The default.
> 
> The comment on the struct says:
>     bool ntsenable;             /* enable NTS on this ntpd instance */
> 
> 
> The first says "service" rather than "server".
> The latter could mean client side too.

On my list.

> Are we ever going to want to use anything older than TLS1.2?  Spec says no, 
> but it might be interesting for testing.

I'm not interested in complicating our lives with a surfeit of obsolete APIs.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

My work is funded by the Internet Civil Engineering Institute: https://icei.org
Please visit their site and donate: the civilization you save might be your own.