2 ms·
>> I was involved in a paid audit of Wire so I know more about the encryption protocol than I do about the other clients Seeing as you mentioned Threema in the
by traceroute66 6y ago
>> I was involved in a paid audit of Wire so I know more about the encryption protocol than I do about the other clients
Seeing as you mentioned Threema in the same post, I think I ought to step in here.
The encryption protocol for Threema is open source, using standard algorithms, not something they invented.
You, like I did for $my_org, can write your own software to send messages to devices running Threema using the Threema API.
Message contents are, of course, encrypted before submission to the API. Threema provide a number of SDKs to help you, but you are under no obligation to use it, you can write your own API submission client from scratch.
P.S. Not saying Wire is bad here. Wire is good. I use it alongside Threema myself for $other_uses. But I'm saying don't write off Threema under a false understanding that their encryption protocols are closed source.
- Aachen 6y agoThat's a good point. Threema using standard libsodium cryptoboxes makes this easier to reimplement than these Axolotl-like protocols. Still, Wire has a bot API so you don't need to reinvent the wheel to integrate in a chat. Not sure that's any harder than using libsodium. Afaik Signal doesn't have an API or SDK, there only seem to be third party implementations for bots.