How the Textsecure Protocol Works

Re:How the Textsecure Protocol Works by tedunangst on Saturday October 15, 2016 @08:26PM (#12716251)

And how are things any different reading source code? The disassembled binary CFG is either going to branch on greater than or greater or equal, exactly like the source code. If you won't see the bug in the CFG, you won't see the bug in the source.

[ Parent | on HN ]

Re:How the Textsecure Protocol Works by conradev on Saturday October 15, 2016 @08:53PM (#12716317)

This is a valid point. Both the source code and the CFG can hide bugs pretty easily.

I would argue that reading source code is much easier, though. For example, if you are auditing code written in a memory-safe language, you don't need to look for memory corruption bugs. You also have an audit trail for all source code changes.

[ Parent | on HN ]

Re:How the Textsecure Protocol Works by tptacek on Sunday October 16, 2016 @12:12AM (#12716844)

It's not like this code was originally written in Haskell. Come on.

[ Parent | on HN ]