Crypto failures are not one mistake repeated. They are four distinct layers of correctness, and each one looks fine from the layer above it.
The code review comment I have written most often, and regretted most often, is
"use a stronger algorithm."
It is regrettable because it is almost never the actual defect. It is the defect I can see
from where I am standing. The team swaps SHA-1 for SHA-256, everyone agrees the review was
useful, and the thing that would have mattered stays where it was.
Every cryptography library says it's secure and performant. Very few can explain how that security...
Most days now, I merge pull requests without reading the diff. That sentence used to describe...
Published by CryptoAgile Labs — Automated security linting and post-quantum cryptographic readiness...
The cheapest bug to catch is the one a reviewer circles on line 40. The expensive one never shows up...
Two separate models — one writing the code, one reviewing the diff — shipped a one-word bug to...
Not every signature error is a cryptographic problem. Most of the time the mess is in the format you picked, the certificate that…
