Today we're announcing a new program in Chrome to make HTTPS certificates secure against quantum computers. The Internet Engineering Task Force (IETF) recently created a working group, PKI, Logs, And Tree Signatures (“PLANTS”), aiming to address the performance and bandwidth challenges that the increased size of quantum-resistant cryptography introduces into TLS connections requiring Certificate Transparency (CT). We recently shared our call to action to secure quantum computing and have written about challenges introduced by quantum-resistant cryptography and some of the steps we’ve taken to address them in earlier blog posts.
To ensure the scalability and efficiency of the ecosystem, Chrome has no immediate plan to add traditional X.509 certificates containing post-quantum cryptography to the Chrome Root Store. Instead, Chrome, in collaboration with other partners, is developing an evolution of HTTPS certificates based on Merkle Tree Certificates (MTCs), currently in development in the PLANTS working group. MTCs replace the heavy, serialized chain of signatures found in traditional PKI with compact Merkle Tree proofs. In this model, a Certification Authority (CA) signs a single "Tree Head" representing potentially millions of certificates, and the "certificate" sent to the browser is merely a lightweight proof of inclusion in that tree.
MTCs enable the adoption of robust post-quantum algorithms without incurring the massive bandwidth penalty of classical X.509 certificate chains. They also decouple the security strength of the corresponding cryptographic algorithm from the size of the data transmitted to the user. By shrinking the authentication data in a TLS handshake to the absolute minimum, MTCs aim to keep the post-quantum web as fast and seamless as today’s internet, maintaining high performance even as we adopt stronger security. Finally, with MTCs, transparency is a fundamental property of issuance: it is impossible to issue a certificate without including it in a public tree. This means the security properties of today’s CT ecosystem are included by default, and without adding extra overhead to the TLS handshake as CT does today.
Chrome is already experimenting with MTCs with real internet traffic, and we intend to gradually build out our deployment such that MTCs provide a robust quantum-resistant HTTPS available for use throughout the internet.
Broadly speaking, our rollout spans three distinct phases.
This area is evolving rapidly. As these phases progress, we will continue our active participation in standards bodies such as the IETF and C2SP, ensuring that insights gathered from our efforts flow back towards standards, and that changes in standards are supported by Chrome and the CQRS.
We view the adoption of MTCs and a quantum-resistant root store as a critical opportunity to ensure the robustness of the foundation of today’s ecosystem. By designing for the specific demands of a modern, agile, internet, we can accelerate the adoption of post-quantum resilience for all web users.
We expect this modern foundation for TLS to evolve beyond current ecosystem norms and emphasize themes of security, simplicity, predictability, transparency and resilience. These properties might be expressed by:
To secure the future of the web, we are dedicating our operational resources to two vital parallel tracks. First, we remain fully committed to supporting our current CA partners in the Chrome Root Store, facilitating root rotations to ensure existing non-quantum-resistant hierarchies remain robust and conformant with the Chrome Root Program Policy. Simultaneously, we are focused on building a secure future by developing and launching the infrastructure required to support MTCs and their default use in Chrome. We also expect to support “traditional” X.509 certificates with quantum-resistant algorithms for use only in private PKIs (i.e., those not included in the Chrome Root Store) later this year.
As we execute and refine our work on MTCs, we look forward to sharing a concrete policy framework for a quantum-resistant root store with the community, and are excited to learn and define clear pathways for organizations to operate as Chrome-trusted MTC CAs.
Post a Comment
No comments :
Post a Comment
Facts Only
Google Chrome is announcing a new program to secure HTTPS certificates against quantum computers.
The IETF has created a working group called PKI, Logs, And Tree Signatures (PLANTS) to address performance challenges in quantum-resistant cryptography for TLS.
Chrome is developing Merkle Tree Certificates (MTCs) as an alternative to traditional X.509 certificates.
MTCs use compact Merkle Tree proofs instead of serialized signature chains.
A Certification Authority (CA) signs a single "Tree Head" representing millions of certificates in the MTC model.
MTCs aim to reduce bandwidth penalties associated with post-quantum cryptography.
Chrome is experimenting with MTCs in real internet traffic.
The rollout will occur in three phases, though specifics are not detailed.
Chrome will continue supporting current CA partners while developing MTC infrastructure.
Traditional X.509 certificates with quantum-resistant algorithms will be supported for private PKIs later this year.
Chrome plans to share a policy framework for a quantum-resistant root store.
The initiative involves collaboration with standards bodies like the IETF and C2SP.
Executive Summary
Google Chrome is introducing a new program to secure HTTPS certificates against quantum computing threats. The initiative focuses on Merkle Tree Certificates (MTCs), a novel approach developed in collaboration with the IETF's PLANTS working group. MTCs replace traditional X.509 certificate chains with compact Merkle Tree proofs, reducing bandwidth and improving efficiency while maintaining security. Chrome is already testing MTCs with real internet traffic and plans a phased rollout to ensure scalability and quantum resilience. The strategy includes supporting current CA partners while building infrastructure for MTCs, with traditional quantum-resistant X.509 certificates reserved for private PKIs. The goal is to maintain high performance and transparency in TLS handshakes, ensuring the web remains secure and fast as quantum-resistant cryptography is adopted.
The approach emphasizes security, simplicity, and resilience, with Chrome committing to active participation in standards bodies like the IETF and C2SP. While the timeline remains fluid, the company aims to define a policy framework for a quantum-resistant root store and enable organizations to operate as trusted MTC CAs. The transition reflects a broader effort to future-proof web security without sacrificing performance or user experience.
Full Take
**Steelman:** Chrome’s initiative to adopt Merkle Tree Certificates (MTCs) is a forward-thinking response to the looming threat of quantum computing. By replacing bulky X.509 certificate chains with lightweight Merkle proofs, the proposal addresses a critical bottleneck in post-quantum cryptography—bandwidth and performance. The emphasis on transparency by design (via public tree inclusion) and the phased rollout demonstrate a measured approach to ecosystem-wide adoption. Credit is due for acknowledging the trade-offs between security and usability, a rare balance in tech policy.
**Pattern Scan:** The narrative leans heavily on technical authority (IETF, C2SP) and future-proofing rhetoric, which could subtly frame resistance as shortsighted. The omission of specific timelines or potential downsides (e.g., CA centralization risks) might reflect a strategic focus on momentum over critique. However, no overt manipulation patterns are detected—this appears to be a genuine engineering-driven proposal.
**Root Cause:** The paradigm here is *preemptive security*—a belief that quantum threats are inevitable and that proactive infrastructure changes are necessary. The unstated assumption is that the current PKI model is too cumbersome for post-quantum algorithms, requiring a fundamental redesign. This echoes historical shifts (e.g., IPv6 adoption) where backward compatibility was sacrificed for long-term scalability.
**Implications:** For human agency, this could democratize access to quantum-resistant security by reducing reliance on resource-intensive PKI. However, it also centralizes trust in Chrome’s root store and MTC CAs, potentially marginalizing smaller players. Second-order effects may include accelerated obsolescence of legacy systems and new attack surfaces in Merkle tree implementations.
**Bridge Questions:**
How might MTCs affect the decentralization of trust in the web’s security model?
What safeguards are needed to prevent CA monopolization under this new system?
Could the bandwidth savings of MTCs be offset by new computational overheads?
**Counterstrike Scan:** A bad-actor playbook would exaggerate quantum threats to justify rushed adoption of proprietary solutions, but Chrome’s transparency about phased testing and standards collaboration mitigates this. The content aligns with legitimate security evolution, not coercion.
*Patterns detected: none*
Sentinel — Human
The article exhibits strong human authorship signals, with technical precision and advocacy consistent with a corporate engineering blog. Minimal stylometric or coordination red flags suggest low likelihood of synthetic origin.