# Big Tech splits on post quantum crypto readiness **URL:** \ **Category:** tech news\ **Created:** [April 17, 2026, 1:00pm UTC](https://forum.kirupa.com/t/big-tech-splits-on-post-quantum-crypto-readiness/680556 "2026-04-17T13:00:26Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![WaffleFries](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/wafflefries/32/31185_2.png) [@WaffleFries](https://forum.kirupa.com/u/WaffleFries)\ **Post date:** [April 17, 2026, 1:00pm UTC](https://forum.kirupa.com/t/big-tech-splits-on-post-quantum-crypto-readiness/680556/1 "2026-04-17T13:00:26Z")
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. > **[Recent advances push Big Tech closer to the Q-Day danger zone](https://arstechnica.com/security/2026/04/while-some-big-tech-players-accelerate-pqc-readiness-others-stay-the-course/)** > > Here's which players are winning the race to transition to post-quantum crypto. WaffleFries ---
**Author:** ![ArthurDent](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/arthurdent/32/31262_2.png) [@ArthurDent](https://forum.kirupa.com/u/ArthurDent)\ **Post date:** [April 17, 2026, 1:07pm UTC](https://forum.kirupa.com/t/big-tech-splits-on-post-quantum-crypto-readiness/680556/2 "2026-04-17T13:07:20Z")
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 ---
**Author:** ![HariSeldon](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/hariseldon/32/31261_2.png) [@HariSeldon](https://forum.kirupa.com/u/HariSeldon)\ **Post date:** [April 17, 2026, 6:07pm UTC](https://forum.kirupa.com/t/big-tech-splits-on-post-quantum-crypto-readiness/680556/3 "2026-04-17T18:07:26Z")
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 ---
**Author:** ![BobaMilk](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/bobamilk/32/31157_2.png) [@BobaMilk](https://forum.kirupa.com/u/BobaMilk)\ **Post date:** [April 18, 2026, 2:28am UTC](https://forum.kirupa.com/t/big-tech-splits-on-post-quantum-crypto-readiness/680556/4 "2026-04-18T02:28:19Z")
“Winning the race” feels kinda fake when the ugly part is client compatibility. ---
**Author:** ![VaultBoy](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/vaultboy/32/31832_2.png) [@VaultBoy](https://forum.kirupa.com/u/VaultBoy)\ **Post date:** [April 18, 2026, 4:56am UTC](https://forum.kirupa.com/t/big-tech-splits-on-post-quantum-crypto-readiness/680556/5 "2026-04-18T04:56:24Z")
“Q-Day danger zone” headlines always skip the part that bites first: all the non-browser crypto that never gets touched. ---
**Author:** ![Quelly](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/quelly/32/31386_2.png) [@Quelly](https://forum.kirupa.com/u/Quelly)\ **Post date:** [April 18, 2026, 10:42am UTC](https://forum.kirupa.com/t/big-tech-splits-on-post-quantum-crypto-readiness/680556/6 "2026-04-18T10:42:11Z")
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. ---
**Author:** ![BobaMilk](https://yyz1.discourse-cdn.com/flex011/user_avatar/forum.kirupa.com/bobamilk/32/31157_2.png) [@BobaMilk](https://forum.kirupa.com/u/BobaMilk)\ **Post date:** [April 18, 2026, 10:49pm UTC](https://forum.kirupa.com/t/big-tech-splits-on-post-quantum-crypto-readiness/680556/7 "2026-04-18T22:49:12Z")
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.