Conversations (XMPP messenger) and its OTR support #447

New Issue

2018-04-17T16:35:26Z

ghost commented

2018-04-17 16:35:26 +00:00

(Migrated from github.com)

Conversations 2.x dropped OTR support while the main developer announced to continue supporting OTR in Conversations Legacy. However, there are at least two discussions (siacs/Conversations#2908, siacs/Conversations#2943) which give the impression that the OTR implementation in Conversations was/is somewhat insecure and the developer knew it.

privacytools.io currently states "Supports end-to-end encryption with either OMEMO, OTR or openPGP." So, we should either remove OTR or add that there is a Legacy version still supporting it.

Conversations 2.x dropped OTR support while the main developer announced to continue supporting OTR in Conversations Legacy. However, there are at least two discussions (siacs/Conversations#2908, siacs/Conversations#2943) which give the impression that the OTR implementation in Conversations was/is somewhat insecure and the developer knew it. privacytools.io currently states "Supports end-to-end encryption with either OMEMO, OTR or openPGP." So, we should either remove OTR or add that there is a Legacy version still supporting it.

ghost commented

2018-04-17 17:04:55 +00:00

(Migrated from github.com)

Create a PR. We could both remove OTR and state that Legacy supports it.

Kcchouette commented

2018-12-20 09:18:50 +00:00

(Migrated from github.com)

Can you close the issue @Shifterovich @infosec-handbook @privacytoolsIO please, as the website already state about Conversation - OMEMO and Conversation Legacy - OTR?
Thank you

Can you close the issue @Shifterovich @infosec-handbook @privacytoolsIO please, as the website already state about Conversation - OMEMO and Conversation Legacy - OTR? Thank you

ghost commented

2018-12-20 12:49:30 +00:00

(Migrated from github.com)

Thanks for helping with issue cleanup @Kcchouette

This repo is archived. You cannot comment on issues.