Google quantum-proofs HTTPS by squeezing 2.5kB of data into 64-byte space - Ars Technica
Summary
Google introduces a method to secure HTTPS certificates against quantum attacks by utilizing Merkle Trees, significantly reducing the data size needed for quantum-resistant cryptography.
Why It Matters
As quantum computing advances, traditional cryptographic methods face potential vulnerabilities. Google's approach to quantum-proofing HTTPS certificates is crucial for maintaining internet security and ensuring that users are not left behind during this transition. The implementation of Merkle Trees offers a scalable solution that balances security and performance.
Key Takeaways
- Google's new method reduces the size of quantum-resistant certificates from 2.5kB to approximately 64 bytes.
- Merkle Trees allow for efficient verification of large data sets without compromising security.
- The transition aims to prevent potential attacks from quantum computers using Shor's algorithm.
- Cloudflare is testing the new Merkle Tree Certificates with a limited number of TLS certificates.
- The initiative enhances the existing Chrome Root Store to ensure robust security against future threats.
Text settings Story text Size Small Standard Large Width * Standard Wide Links Standard Orange * Subscribers only Learn more Minimize to nav Google on Friday unveiled its plan for its Chrome browser to secure HTTPS certificates against quantum computer attacks without breaking the Internet. The objective is a tall order. The quantum-resistant cryptographic data needed to transparently publish TLS certificates is roughly 40 times bigger than the classical cryptographic material used today. Today’s X.509 certificates are about 64 bytes in size, and comprise six elliptic curve signatures and two EC public keys. This material can be cracked through the quantum-enabled Shor’s algorithm. Certificates containing the equivalent quantum-resistant cryptographic material are roughly 2.5 kilobytes. All this data must be transmitted when a browser connects to a site. The bigger they come, the slower they move “The bigger you make the certificate, the slower the handshake and the more people you leave behind,” said Bas Westerbaan, principal research engineer at Cloudflare, which is partnering with Google on the transition. “Our problem is we don’t want to leave people behind in this transition.” Speaking to Ars, he said that people will likely disable the new encryption if it slows their browsing. He added that the massive size increase can also degrade “middle boxes,” which sit between browsers and the final site. To bypass the bottleneck, companies are turning to Merkle Trees, a dat...
![[2603.14267] DiFlowDubber: Discrete Flow Matching for Automated Video Dubbing via Cross-Modal Alignment and Synchronization](https://arxiv.org/static/browse/0.3.4/images/arxiv-logo-fb.png){kind=logo}