[ANN] Specification update

Philip Linde linde.philip at gmail.com
Mon Nov 8 16:14:18 GMT 2021
Hi Stephane!

On Mon, 8 Nov 2021 16:18:11 +0100
Stephane Bortzmeyer <stephane@sources.org> wrote:

> On Mon, Nov 08, 2021 at 09:28:41AM -0500,
>  Jason McBrayer <jmcbray@carcosa.net> wrote 
>  a message of 15 lines which said:
> 
> > Please let me know if carcosa.net is among those.
> 
> Indeed it is :-(
> 
> % agunua carcosa.net
> Warning, no TLS shutdown received from the server

Very useful. I have not considered TLS in detail myself, but I tested
this just now with the Go TLS implementation which does seem to send
the proper notification as you call Close on connections. Good news for
people writing server implementations in Go, I think.

I wonder how hard it would be to automatically identify server software
that doesn't implement this properly. Probably some server software
could be differentiated based on their error code descriptions or how
they deal with some corner cases. If we could trace these capsules to a
few server implementations it might not be too much work to reach out
to the authors and poke at them about the spec change.

With the numbers you suggested earlier, I am wary of strictly enforcing
close_notify in my client, but in the interim maybe client authors
could warn as yours does, or provide some way to add domains to an
exception list.

-- 
Philip


Archive home | About this archive