How the Textsecure Protocol Works

Re:How the Textsecure Protocol Works by frutiger on Saturday October 15, 2016 @04:46PM (#12715583)

If builds were reproducible (i.e. binaries would be identical if recompiled with the same toolchain on a different machine), then all it would take is N independent builders to verify the app store binary matches their locally built binary to greatly decrease the likelihood of tampering.

So, while being open source is not the complete answer, it certainly doesn't hurt.

[ Parent | on HN ]

Re:How the Textsecure Protocol Works by tedunangst on Saturday October 15, 2016 @05:44PM (#12715782)

How do you guarantee the App Store doesn't serve limited edition binaries to selected recipients?

[ Parent | on HN ]

Re:How the Textsecure Protocol Works by nmgsd on Saturday October 15, 2016 @06:21PM (#12715893)

The App Store run by a central authority with complete control over what can even be available and the ability to modify the delivery at their own whim is certainly a big issue in terms of trusting the integrity of the apps running on a device.

[ Parent | on HN ]

Re:How the Textsecure Protocol Works by verbify on Saturday October 15, 2016 @07:08PM (#12716034)

If you suspect yourself to be a selected recipient (e.g. you're Edward Snowden) I reckon you should compile your own binaries. Or read 'Reflections on Trusting Trust'.

[ Parent | on HN ]

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

Now you are the selected recipient of modified source code.

[ Parent | on HN ]

Re:How the Textsecure Protocol Works by verbify on Sunday October 16, 2016 @12:46PM (#12719488)

Get it from multiple sources, and do a diff.

[ Parent | on HN ]

Re:How the Textsecure Protocol Works by conradev on Saturday October 15, 2016 @07:16PM (#12716060)

Fun fact: The App Store already serves limited edition binaries to everyone because it encrypts them per-account :)

[ Parent | on HN ]

Re:How the Textsecure Protocol Works by Canada on Saturday October 15, 2016 @06:30PM (#12715923)

Forget the aop store. How do we know Google, Apple, Microsoft, Ubuntu, etc doesn't give us a malicious kernel update?

I don't think we have good solutions for the problem of malicious updates in general.

The only one I can think of is a trusted hypervisor that hashes memory in the guest and reports on it. And even then, how do we trust that?

[ Parent | on HN ]

Re:How the Textsecure Protocol Works by angry_octet on Saturday October 15, 2016 @08:31PM (#12716264)

Forget the software, the firmware running on the baseband processor can read system memory and send it over the network without you knowing. But that takes lots of effort to target a specific person.

So what do you do? It comes back to making sure that 'they' can only hack some of the people all the time, and all of the people some of the time. It's preventing them hacking all the people all the time I worry about.

[ Parent | on HN ]

Re:How the Textsecure Protocol Works by tptacek on Saturday October 15, 2016 @05:05PM (#12715639)

I don't think it hurts! All else being equal, I'd rather have source than not have it. What I don't accept is our supposed helplessness in detecting backdoors in secure messaging software.

[ Parent | on HN ]

Re:How the Textsecure Protocol Works by ChoHag on Saturday October 15, 2016 @05:01PM (#12715629)

Or we could have build systems that weren't even more convoluted and fragile than they were 50 years ago and just release software in the form it's supposed to be in.

[ Parent | on HN ]