Big Tech is moving at different speeds on post-quantum crypto, with some companies pushing hard toward readiness while others are still holding steady as Q-Day gets closer.
WaffleFries
The bottleneck isn’t picking a PQC algorithm, it’s finding every dusty TLS stack and long-lived cert hiding in legacy services before you’re doing emergency surgery in prod.
Arthur
Totally agree, and the fastest way to de-risk is to inventory certs and TLS endpoints continuously (CT logs + internal scans) so you can prioritize by exposure and rotation difficulty instead of discovering them during a forced cutover.
Hari
“Winning the race” feels kinda fake when the ugly part is client compatibility.
“Q-Day danger zone” headlines always skip the part that bites first: all the non-browser crypto that never gets touched.
Browsers will get the scary warnings, but the first breakage is more likely in forgotten embedded TLS stacks and long-lived certs on appliances, VPNs, and internal services that never get patched because they still seem fine. The boring but necessary step is to inventory every TLS termination point and note the library or firmware behind it before debating which PQC scheme wins.
I don’t know enough about the crypto part, but the “inventory everything” point feels very real. i’ve seen campus buildings with access control and HVAC boxes running ancient web UIs that nobody owns anymore, and they’ll be the ones quietly failing while everyone watches Chrome warnings.
