3 ms·
On a side note, why expose ALL users to legacy TLS ciphersuites to support a small number of users? It would be nice if there was a way to send legacy browsers
by sitkack 9y ago
On a side note, why expose ALL users to legacy TLS ciphersuites to support a small number of users? It would be nice if there was a way to send legacy browsers and ciphersuites to
legacybrowser.example.com
I don't know of a clean way to do that and not expose all users to the bad suites. If future versions of HTTP could encode a retry url on connection negotiation it would definitely help.
Ideas?
- eridius 9y agoTerminate the TLS at a load balancer and have the load balancer detect the weak ciphersuite and send the traffic to a separate server? That server can then redirect to legacybrowser.example.com, or just serve up the content that you would get if you went to that domain.
- sitkack 9y agoI'd like it so if any old cipher suite is negotiated, it is then redirected to `legacybrowser.example.com` so that main traffic would ONLY use high quality cipher suites. One might even limit what the user could do using the insecure connection.
- eridius 9y agoAnd that's what my proposal does. All the traffic that goes to your normal servers comes from clients that used high quality cipher suites, and all the clients that negotiated weak cipher suites end up talking to a separate server entirely.
- bcoates 9y agoI think the only reliable way to prevent downgrade attacks in the face of potentially arbitrarily broken old versions is to have a field in the server certificate promising that the server supports particular protocol versions. If that were in place, if a client that supports TLS 1.3 received a cert that says "all servers on example.org support TLS 1.3 (and also possibly older or newer versions)" then the client would refuse to downgrade even if the server needed to offer old protocols for old clients. Otherwise whatever mechanism you use to send old clients to legacybrowser.example.com could (potentially) be corrupted to trick non-legacy browsers into going there.
- sitkack 9y agoI was also thinking that the connection terminator would only let legacy clients use the legacy endpoint, at at least known-non-legacy clients would be forced to communicate with the TLS 1.3 endpoint.