Yo Eric! On Fri, 1 Feb 2019 10:19:53 -0500 (EST) "Eric S. Raymond via devel" <devel@ntpsec.org> wrote:
> I have enhanced the configuration parser to process NTS client-side
> configuration options. The configuration state is available to the
> nts.c hooks as members of a structure passed to them, along with the
> dynamic NTS state (stored cookies) and the parsed content of the
> current packet.
What structure name?
> Having a separate nts config statement would have required admins to
> enter the name of a server to which secure connection is intended
> twice, once in the server declaration and once in the nts declaration.
Uh, no. 'server' OR 'nts'. Never both.
> This was suboptimal design, inviting subtle configuration bugs due to
> typos.
Or rather, suboptimal reading. Combining them was discarded by every
one days ago. Too many options conflict in non-obvious ways.
> Accordingly, the nts configuration stuff is implemented in a way that
> conforms to good DRY (Don't Repeat Yourself) architectural practice.
> That is, as options to the "server" declaration.
I can't find this in nts.adoc... Where?
RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
g...@rellim.com Tel:+1 541 382 8588
Veritas liberabit vos. -- Quid est veritas?
"If you can’t measure it, you can’t improve it." - Lord Kelvin
pgpuyI0MiU2iA.pgp
Description: OpenPGP digital signature
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
