3 ms·
> Couldn't the client send SNI after the DH and then the server authenticate the secret? That means you can't use sni to route your request to a different serv
by ori_b 9y ago
> Couldn't the client send SNI after the DH and then the server authenticate the secret?
That means you can't use sni to route your request to a different server.
- infogulch 9y agoYes, whatever is serving on that interface will have to terminate TLS. Or somehow pass the session information to the proxied server, or ask the client to reconnect, or do some kind of tls tunneling from the client to the real host. I don't think any of those are unreasonable options.