You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] TCP TLS handshakes fail because the peer hostname is missing #16589
Connect NettyClient or NettyConnectionClient to a TLS server with a trusted certificate whose SAN matches the target address. Configure the client certificate, key and CA through SslConfig.
TCP connects, but the first TLS handshake fails:
SSLHandshakeException: (certificate_unknown) Hostname or IP address is undefined.
SslClientTlsHandler creates the engine with newEngine(alloc), leaving the peer host unset. Netty 4.2 enables HTTPS endpoint verification by default.
What you expected to happen
A trusted certificate with a matching SAN should complete the handshake. A mismatched SAN should still be rejected.
Anything else
Related to #16200, which addresses the QUIC client. This affects the TCP client pipeline in dubbo-remoting-netty4.
Reproduced with a CA-signed server certificate for 127.0.0.1. Passing the connection address to the TLS engine allows the handshake; a certificate from the same CA with SAN 127.0.0.2 is still rejected.
Do you have a (mini) reproduction demo?
Yes, I have a minimal reproduction demo to help resolve this issue more effectively!
Are you willing to submit a pull request to fix on your own?
Yes I am willing to submit a pull request on my own!
Activity
Tighten TCP TLS hostname regression coverage
Pass the peer address to the TCP TLS client engine (apache#16590)