2 ms·
> Or is there something more practical you're referring to? I would probably compile the reference source and use BinDiff[1] (or a handful of other tools) to c
by woodruffw 4y ago
> Or is there something more practical you're referring to?
I would probably compile the reference source and use BinDiff[1] (or a handful of other tools) to compare it with the official binary. I've used BinDiff successfully for similar purposes in the past; it's also a popular tool for finding N-days after patches go out.
Signal could patch in that kind of backdoor, sure. But it's still globally disclosed in that case: you're revealing your backdoor to every prospective reverse engineer (there's a lot of them!), even if you only selectively enable it. Signal can probably be about as confident that nobody is reading their machine code as Chrome can, which is to say not confident.
And note: you don't need a solid enough mental model of how the system works at the machine level. You only need a differential understanding of what the public code says and what the machine code does, which is much easier.
Is it possible? Sure. But it's much, much higher risk and visibility than every other technique available to nation-state adversaries.
[1]: https://www.zynamics.com/bindiff.html https://www.zynamics.com/bindiff.html