> On May 9, 2018, at 10:07 PM, Martin Thomson <[email protected]> wrote:
>
> This alert is actually fairly common (though I'm surprised to see OpenSSL
> still doing it) and clients need to handle it, unfortunately.
I may be misreading the code, but it sure looks like the alert is only
sent if the application callback for the server name extension asks
OpenSSL to do that. The application can just decline the extension
and let the handshake continue with a default certificate... Is
the surprise that the alert is sent, or that it is a warning, or
something else?
--
--
Viktor.
_______________________________________________
TLS mailing list
[email protected]
https://www.ietf.org/mailman/listinfo/tls
