omemo: implement end-to-end encryption using XEP-0384 #291

Open
opened 2022-05-01 11:26:22 +00:00 by SamWhited · 0 comments

The OMEMO end-to-end (e2e) encryption protocol is widely used among XMPP clients. There are two versions currently used in the wild: version 2, documented in XEP-0384: OMEMO Encryption, and "siacs OMEMO" documented in an older version of the spec v0.3.0. We could implement one, the other, or both. If implementing v0.3.0 it should live in mellium.im/legacy/omemo, if implementing the current version it can live in its own module to start, eg. mellium.im/omemo and we can decide what to do with it before it becomes ready for wide spread use.

The OMEMO end-to-end (e2e) encryption protocol is widely used among XMPP clients. There are two versions currently used in the wild: version 2, documented in [XEP-0384: OMEMO Encryption], and "siacs OMEMO" documented in an older version of the spec [v0.3.0]. We could implement one, the other, or both. If implementing v0.3.0 it should live in `mellium.im/legacy/omemo`, if implementing the current version it can live in its own module to start, eg. `mellium.im/omemo` and we can decide what to do with it before it becomes ready for wide spread use. [XEP-0384: OMEMO Encryption]: https://xmpp.org/extensions/xep-0384.html [v0.3.0]: https://xmpp.org/extensions/attic/xep-0384-0.3.0.html#usecases
Sign in to join this conversation.
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: mellium/xmpp#291
There is no content yet.