TLS 1.3 is not happening, because shitty vendors https://www.ietf.org/mail-archive/web/tls/current/msg24517.html …
My point is that those changes could have been made 6 months, 12 months, and actually even 48 months ago, as we've always known about this.
-
-
it seems google is trying to do that now, we'll see. I'm not happy with the approach, but if it works it may be the least bad solution.
-
but there could be situations where you'd have to sacrifice new features, e.g. middleboxes not accepting RTT changes
-
This "if MitM boxes break anything work around it" approach is kinda problematic: it does not necessitate people to actually fix the setup.
-
Fix being either disabling them entirely (best) or ask the vendor to fix. Google simply enforcing TLS 1.3 might be a good solution for once.
End of conversation
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.