Re: Getting ready for a release, wildcards

2022-04-20 Thread Hal Murray via devel
[The mail system is in sloth mode again.] matthew.sel...@twosigma.com said: > I don't think we should have a knob for disabling wildcards. This is not the > sort of knob that operators expect (what other software provides such a > knob?) and we're just adding another code path to test. I'll be in

Re: Getting ready for a release, wildcards

2022-04-20 Thread Matt Selsky via devel
Hi Hal, I don't think we should have a knob for disabling wildcards. This is not the sort of knob that operators expect (what other software provides such a knob?) and we're just adding another code path to test. Are there any other release blockers? If not, I'll update the NEWS for the user-

Re: Release, wildcards, etc

2022-04-20 Thread Matt Selsky via devel
Hi Hal, I'd like to get https://gitlab.com/NTPsec/ntpsec/-/merge_requests/1264 merged and then do the release. Is there anything else that we want in the release? Thanks, -Matt ___ devel mailing list devel@ntpsec.org https://lists.ntpsec.org/mailman/

Getting ready for a release, wildcards

2022-04-20 Thread Hal Murray via devel
I just pushed 2 tweaks. One is to update the nts cert documentation to say that it doesn't do any checking on the certificate. The other is a hack patch to aes_siv.c to supress deprecated warnings from OpenSSL 3. Is anybody (else) using OpenSSL 3? It's trivial on FreeBSD. Just install open

Release, wildcards, etc

2022-04-20 Thread Hal Murray via devel
> Sigh. I should get up to speed onmn crypto and certificates. I doubt I can > do it fast enough to be useful on this one, though. Service Names in TLS https://datatracker.ietf.org/doc/draft-ietf-uta-rfc6125bis/ It's 24 pages with the usual amount of boiler plate so only half of that is ser