How the Textsecure Protocol Works

Re:How the Textsecure Protocol Works by FabHK on Saturday October 15, 2016 @04:39PM (#12715559)

Wire seems fairly fully featured, open source, and claim to have a feasible "freemium" business model, i.e. later selling premium services on the platform.

They claim they use the Axolotl double ratchet, though Moxie/OWS claims Wire uses a variation of the protocol they don't recommend.

[ Parent | on HN ]

Re:How the Textsecure Protocol Works by niftich on Saturday October 15, 2016 @06:20PM (#12715891)

If you're interested about this topic, I recommend the following readings previously posted on HN and drawing your own conclusions. They are listed in no particular order: [1][2][3][4]

[1] https://news.ycombinator.com/item?id=12148728

[2] https://news.ycombinator.com/item?id=12361410

[3] https://hn.algolia.com/?query=%22wire%20does%20not%20use%22%...

[4] (long but enlightening read) https://news.ycombinator.com/item?id=11725602

[ Parent | on HN ]

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

I would be interested to know exactly what it is about Wire that OWS doesn't seem to approve of

[ Parent | on HN ]

Re:How the Textsecure Protocol Works by eatbitseveryday on Sunday October 16, 2016 @01:19AM (#12717101)

> Wire does not use Signal Protocol, they used some of our code to create a protocol of their own devising that we do not recommend.

4 days ago, no follow-ups to questions for details.

https://news.ycombinator.com/item?id=12688012#12690148

[ Parent | on HN ]

Re:How the Textsecure Protocol Works by qznc on Saturday October 15, 2016 @06:01PM (#12715842)

It might just be that they did not look into it.

[ Parent | on HN ]