7 ms·
TextSecure doesn't use OTR, it uses a construction based on the Axolotl ratchet as described here: https://github.com/trevp/axolotl/wiki https://github.com/tre
by rakoo 12y ago
TextSecure doesn't use OTR, it uses a construction based on the Axolotl ratchet as described here:
https://github.com/trevp/axolotl/wiki https://github.com/trevp/axolotl/wiki
It's much much better than OTR in that:
- Asynchronicity is on by default (you don't need both parties to be up and running at the same time to start a convo)
- You don't need to wait for your recipient to answer before you can write something (ie you can send multiple messages one after another, directly)
- Because you can do both of the above, you can easily do multiparty, something OTR struggles with.
For more details:
https://whispersystems.org/blog/asynchronous-security/ https://whispersystems.org/blog/asynchronous-security/
https://whispersystems.org/blog/private-groups/ https://whispersystems.org/blog/private-groups/
- andyjohnson0 12y agoYou're right and I was wrong. The TextSecure protocol was originally based on OTR, but I hadn't appreciated the degree of divergence from it required by their introduction of asynchronous ephemeral key negotiation. So, thanks! I learned about some cool stuff.