XEP-0384: OMEMO encryption support #10
Labels
No labels
Kind: Bug
Kind: Documentation
Kind: Enhancement
Kind: Feature
Kind: Question
Priority: High
Priority: Low
Priority: Medium
Reviewed: duplicate
Reviewed: invalid
Status: Completed
Status: help wanted
Status: In progress
Status: wontfix
XEP
No milestone
No project
No assignees
6 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Anoxinon_e.V./xmppc#10
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It would be cool if xmppc could support OMEMO encryption for chats. Some basics are already there with the finperprint list etc.
But I totally understand that this would not become top priority, because implementing OMEMO isn't that easy.
OMEMO Encryption Supportto OMEMO encryption supportOMEMO encryption supportto XEP-0384: OMEMO encryption supportI'm surprised that none of the CLI-clients for XMPP haven't already implemented support for OMEMO in 2023.
I would love to see this feature in anyone of them, especially in xmppc. :)
The libervia cli client has omemo support, just as the tui client poezio. Your statement is wrong, thus. @Hund
liberviadoes support OMEMO, and it has a command line interface,libervia-cli:The latter, OX, is also supported by
go-sendxmpp, btw.Thanks. libervia is unfortunately, not available for, me in my repositories.
Isn't OXIM just E2EE via OpenPGP? I'm pretty sure that no sane person have, voluntary, ever been using PGP. ;)
@Hund OX is the new implementation of PGP in xmpp and I see future in OX. You can build libervia on your own.
First question about OMEMO Support in xmppc: How should we get and trust the OMEMO keys?
Getting is easy: There is a PEP node with all device keys for it.
Trust depends on trust policy. E.g. xmppc could BTBV (blind trust before verification) by default.
It could also show fingerprints and let user accept or reject a key.
In any case, xmppc must store received keys locally (in a file or database) together with the trust status (unverified, verified, rejected).
Things are slightly easier with OX, I guess: Only user identity keys, no device keys, therefore less fingerprints to verify.
Ok, we need a kind of trustmode like I did for profanity. In some cases TOFU is nice. But it will not work well, if you change your devices / software often
BTW: iNPUTmice/Conversations#155
happy new year 2024 :P
meow :)
I will try to work on a xmpp lib. Currently it's a "Proof of concept". When the lib will work well, I will change the implementation of xmppc to use this lib. Also, I will try to implement OMEMO within this new library.