4 ms·
Quantum-Proof ClientHello Messages: How Size Causes Server Failures
- skilled 2y agoSome additional context, Q1 2024 Summary from Chrome Security (https://groups.google.com/a/chromium.org/g/chromium-dev/c/K_HO5LsPDKc?pli=1 https://groups.google.com/a/chromium.org/g/chromium-dev/c/K_...) > After several months of experimentation for compatibility and performance impacts, we’re launching a hybrid postquantum TLS key exchange to desktop platforms in Chrome 124. This protects users’ traffic from so-called “store now decrypt later” attacks, in which a future quantum computer could decrypt encrypted traffic recorded today. Chrome 124 Breaks TLS Handshake (https://www.reddit.com/r/sysadmin/comments/1carvpd/chrome_124_breaks_tls_handshake/ https://www.reddit.com/r/sysadmin/comments/1carvpd/chrome_12...) > Apparently Chrome 124 changed a setting “TLS 1.3 Hybridized Kyber Support” from disabled to enabled as the default. This appears to break the TLS handshake for servers that do not know what to do with the extra data in the client hello message. > If you mysteriously have a broken web application and the server is sending a reset directly after the client hello, try turning this setting off. In our testing IE mode works as well, probably because this extra data is not transmitted in IE mode while it is in normal Edge.
- fanf2 2y agoThe “I’m a network administrator? How does this affect me?” section seems to be designed to provoke lots of wasted repeat effort. The Google Chrome developers who caused this problem and who created this web site ought to be keeping a list of bug reports and fixes on their web page.