100% agree on everything from @filippo here, this has been my thinking for at least two years:
🜗 🝒 🝲 crypto as in 'cryptography' 🝳 🝡 🜖
¹isogenist, co-host SCWpod
🜗 🝒 🝲 crypto as in 'cryptography' 🝳 🝡 🜖
¹isogenist, co-host SCWpod
100% agree on everything from @filippo here, this has been my thinking for at least two years:
See also @dangoodin 's excellent article:
Objects in the quantum mirror are closer than they appear.
https://blog.google/innovation-and-ai/technology/safety-security/cryptography-migration-timeline/
Dustin Moody from NIST: “you don’t need more than 128 bits of symmetric keys for post-quantum security” #rwc2026
Say it louder, for the people in the back!
At WWDC, we unveiled formally verified ML-KEM and ML-DSA #PostQuantum implementations in CryptoKit.
🆕🎥 Last month at Hexagon in Paris, we provided additional insights into the mechanisms used for verifying the implementations using Cryptol, SAW and Isabelle.
The talk also covers the evolution of the Secure Page Table Monitor, a view into Memory Integrity Enforcement, updates to Apple Security Bounty… and a note on the moral character of offensive security work.
For the past several years I've been trying intermittently to get Cross Translation Unit taint analysis with clang static analyzer working for Firefox. While the efforts _have_ found some impactful bugs, overall the project has burnt out because of too many issues in LLVM we are unable to overcome.
Not everything you do succeeds, and I think it's important to talk about what _doesn't_ succeed just as much (if not more) about what does.
With the help of an LLVM contractor, we've authored this post to talk about our attempts, and some of the issues we'd run into. https://attackanddefense.dev/2025/12/16/attempting-cross-translation-unit-static-analysis.html
I'm optimistic that people will get CTU taint analysis working on projects the size of Firefox, and if you do, well I guess I'll see you in the bounty committee meetings ;)
New blog post: ML-KEM Mythbusting.
Due to reasons.