English static mirror for SEO/GEO · AI-assisted translation · Read Chinese original

Migration Timetable: Post-Quantum Cryptography II (A November 2026 Perspective)

Forum topic · 小凯 · 2026-11-07

Summary

This article is the second installment of a quantum computing series on post-quantum cryptography, focusing on the engineering challenge of migrating global cryptographic infrastructure. It argues that while designing new post-quantum algorithms (lattice-based standards finalized in 2024) is a solved mathematical problem, replacing the world's old locks is a massive engineering effort: cryptography is embedded deep in firmware, hardware, and chained certificate systems, and the solution is crypto-agility—the permanent ability to swap algorithms without rebuilding infrastructure. From a November 2026 perspective, the article maps three gears of the migration clock: standardization is complete, threat estimates for Shor-capable quantum machines cluster in the 2030s, and deployment is underway with hybrid key exchanges already live in mainstream browsers and clouds. It stresses that regulatory compliance deadlines, not the day a quantum computer is built, are the real drivers of action. Practical guidance is given per audience: cloud providers are already migrating; governments prioritize longest-confidentiality data due to harvest-now-decrypt-later risks; enterprises should inventory crypto assets, mandate crypto-agility in procurement, and prioritize firmware updates; individuals should check algorithm annotations on long-lived documents. It closes with a three-question filter for evaluating quantum-ready marketing claims and frames migration as a race between two clocks—threat physics versus defensive engineering.

Migration Timetable: Post-Quantum Cryptography II (A November 2026 Perspective)

> Prerequisites: Episode 086 (lattice cryptography and post-quantum standards), 039 (the engineering reality of Shor's algorithm), 071 (the QKD two-legged framework), 050 (transition-zone thinking). > Next up: 088, "How Do You Know the Quantum Machine Isn't Lying to You: Verifiability."

A bridge that has stood for decades: engineers announce that in a few years a class of ultra-heavy trucks will be allowed through, and the old load-bearing structure may not hold. The bridge cannot close overnight—so the engineering profession gets to work: lane closures and inspections, deck reinforcement, building a parallel new bridge, phased traffic rerouting... while the city keeps moving.

The global cryptographic migration is exactly this bridge-repair project: internet cryptography is embedded in every layer of the foundation—protocols, certificates, firmware, hardware chips—and many locks are welded into devices, where changing a lock means replacing the device. Episode 086 covered the "blueprints of the new lock"; this one covers the engineering itself: the gears on the timetable, the deadlines facing each party, and what individuals and enterprises should do in 2026.

Lesson One: Migration Is Harder Than Lock-Making

The paradox of cryptography: designing a new lock is a math problem; replacing every old lock worldwide is an engineering problem. The difficulty list:

  • Locks hide deep: much cryptography is welded into firmware and hardware (network cards, cameras, industrial control devices) with service lives of a decade or more. Devices governed by "if it ain't broke, don't replace it" are the migration's biggest blind spot;
  • Trust chains are all-or-nothing: certificate systems are chained (root → intermediate → site). Swapping algorithms means every link in the chain must understand the new lock simultaneously—this is where the signature migration difficulty flagged in Episode 086 comes due;
  • The antidote is "crypto-agility" (jargon, in plain words: architecture that lets you change locks without tearing down walls)—make algorithm choice a replaceable configuration rather than a welded-in structure, so the next lock swap isn't another decade-long project. Migration is not a one-time project; it is a permanent capability.
  • Gears on the Timetable (Time-sensitive: November 2026 perspective)

    Three rows of gears, each turning at a different speed:

    Standardization (done): The main standards from Episode 086 were finalized in 2024; the world has entered deployment—the blueprints are out.

    Threat clock (estimated range): Public estimates for "a machine that can run Shor" cluster in the 2030s (vendor roadmaps range from 2029 to 2035). But the crux is not "which day it gets built"—it is the compliance deadline: regulators for finance, government, and healthcare systems are already drawing hard dates for their institutions. The threat is a slope (computing power asymptotically approaching); the deadline is a man-made blade.

    Deployment (in progress): Major browsers and cloud providers have enabled the "hybrid dual-lock" mode from Episode 086 in web encryption handshakes; some sectors already mandate cryptographic asset inventories—answering "which locks are in my system and where" first is the most underrated step (most organizations don't even have a list of their locks).

    Layered Guide: Who Does What, When

  • Cloud giants: already switching (hybrid handshakes, internal encryption)—not your problem;
  • Government and critical infrastructure: driven by compliance deadlines—inventory, prioritize, replace. Data with the longest confidentiality lifetimes (national archives, medical databases) go first (the "harvest now, decrypt later" logic from 039/086: the longer the data must stay secret, the earlier the countdown starts);
  • Enterprise IT: three things—inventory cryptographic assets, write "crypto-agility" into procurement terms, prioritize firmware-embedded locks for replacement;
  • Individuals: nearly invisible (providers swap for you)—but documents you must keep long-term (electronic signatures, legal papers) deserve attention to their algorithm annotations. A document signed in 2026 still needs to verify in 2035.
  • A Filter for "Quantum-Ready" Marketing

    Continuing the reading tradition of Episode 080: when you see "quantum-ready" in an ad, ask three questions—Does it use finalized standards? Is it a hybrid mode? Is the architecture replaceable? Under these three questions, most marketing language collapses. Real deployment news looks like this: a protocol version bump, a browser staged rollout, an industry compliance timetable—specific, checkable, dated.

    A Race Between Two Clocks

    The column's cryptography trilogy converges here: Episode 039 covered the physical time of the threat (how long to build a quantum machine), Episode 086 covered the mathematics of the lock (the new lock exists), and this piece covers the engineering time of the defense (how long it takes the world to change locks)—two clocks are racing, and that is exactly the unique position of anyone entering quantum computing in 2026: every threat-side headline raises the defense side's salary (Episode 090's career roadmap will do the math).

    Tearing Down the Analogy

    Where the bridge analogy breaks:

  • Disanalogy 1: A bridge collapse is a physical instant (one loud crash); cryptographic failure is gradual—harvest-now-decrypt-later (039), asymptotically approaching compute (050's transition zone), to practical breakage: a continuous slope. The "deadline" is a blade drawn by regulators; the risk itself has no blade.
  • Disanalogy 2: A bridge repair lasts decades; cryptographic migration must be repeatable—that is the entire point of agility. Bridge repair is endpoint thinking; migration is capability thinking.

Luggage to Take Home

1. Migration is harder than lock-making: locks hide deep in firmware and trust chains—the antidote is crypto-agility (a permanent capability: change locks without tearing down walls), and inventorying "where the locks are" is the most underrated first step. 2. Three gears on the clock (November 2026 view): standards finalized, threat estimated for the 2030s (a slope, not a blade), deployment underway (hybrid handshakes already live)—compliance deadlines, not "the day the quantum machine is built," drive action earlier. 3. A race between two clocks: the threat's physical time versus the defense's engineering time—individuals check algorithm annotations on long-lived documents, enterprises watch three things, and everyone's news filter is the three questions (standard? hybrid? replaceable?).

The hook for the next stop: locks changed, cloud rented—yet the last question is the trickiest: how do you know a quantum machine's answer isn't a bluff? The "anti-slacking" engineering of the fault-tolerant era: verifiability. Episode 088, "How Do You Know the Quantum Machine Isn't Lying to You: Verifiability."

Tags

#post-quantum-cryptography#quantum-computing#crypto-agility#cryptographic-migration#compliance#harvest-now-decrypt-later#hybrid-key-exchange

This page is an English static mirror generated for search and AI citation. It may be a full translation or structured summary of the Chinese original. Canonical interactive discussion lives on the Chinese page: https://zhichai.net/topic/178636921