Like, the issues I found aren't even particularly difficult to mitigate. I provided some sample code in my Matrix disclosure blog post and pointed to a bitsliced AES implementation (BearSSL) for systems that can't do AES-NI.

Hell, you could probably get a fucking LLM to do it. Trail of Bits published a Claude skill for detecting whether a compiler has undermined the intent for code to be constant-time. But the heavy-lifting is done by a Python script.

Shipping cryptography without side-channels was table-stakes for being taken seriously.

(Note: I'm not endorsing LLM use. This is a flippant remark about how embarrassing the things I found in Matrix's Olm library were.)

The Matrix guy is incentivized to control the narrative here. No surprise there.

But I implore anyone paying attention to critically evaluate the facts and what he said then as well as what he's saying now.