On 2/2/19 9:11 PM, Gary E. Miller via devel wrote: >> tlsversions "1.2 1.3"
> Which would have broken when SSL became TLS, and will break when TLS > becomes XXX. Not really. Roll back the world to SSLv3 being the latest: I would be proposing this: sslversions "2 3" Then the IETF changes the name to TLS and restarts the numbering. That's trivial to address: sslversions "2 3 tls1" So if TLS gets renamed to XYZ, it just becomes: tlsversions "1.2 1.3 xyz1" and make xyzversions an alias for tlsversions. This is really small potatoes. If you want it to be like this, I don't care: tlsversions "tls1.2 tls1.3" But we're still putting tls in the option name, so is that a problem? -- Richard
signature.asc
Description: OpenPGP digital signature
_______________________________________________ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel
