omemo: implement end-to-end encryption using XEP-0384 #291
Labels
No Label
bug
CI
documentation
duplicate
enhancement
good first issue
help wanted
i18n
invalid
needs-investigation
ops
proposal
proposal-accepted
proposal-declined
question
refactor
security
testing
upstream
wontfix
Kind: Breaking
Kind: Bug
Kind: Documentation
Kind: Enhancement
Kind: Feature
Kind: Maintenance
Kind: Question
Kind: Security
Kind: Testing
Priority: Critical
Priority: High
Priority: Low
Priority: Medium
Reviewed: Confirmed
Reviewed: Duplicate
Reviewed: Invalid
Status: Blocked
Status: Completed
Status: Help wanted
Status: In progress
Status: Needs feedback
Status: Stale
No Milestone
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: mellium/xmpp#291
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
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.