OMEMO implementation state/tracking

[COM8]

This issue tracks the state of the OMEMO implementation.

• [x] Prerequisites
  • [x] MUC (XEP-0045) #10
  • [x] Publish-Subscribe (XEP-0060)
  • [x] Bookmarks 2 (XEP-0402)
  • [x] Bookmarks (XEP-0048)
• [x] Key announcement
  • [x] Single chat
  • [x] MUC
• [ ] Building a session
  • [x] Single chat
  • [ ] MUC
• [ ] Encrypt messages
  • [x] Single chat
  • [ ] MUC
• [x] Decrypt messages
  • [x] Single chat
  • [x] MUC
• [ ] UI stuff (requires #50)
  • [x] Display own fingerprint as text
  • [x] Display own fingerprint as QR-Code
  • [x] Display own devices
  • [x] Display contact devices
  • [x] Display contact fingerprint as text
  • [x] ~Display contact fingerprint as QR-Code~
  • [ ] Un-/trust other devices ~ 60%
• [x] #126
• [x] #134
• [ ] #172

[Echolon]

As I suggested to other clients already, encryption should be treated simple for users.

Meaning:

• Show a lock symbol in the chat window

• Be clear about choices: Offer choices as 'Unencrypted' (dont use the plaintext terminology) or 'Encrypted (OMEMO)' (don't use the encryption name only)

Users can neither differ nor decide on whats right. They only know the states on and off. Everything else (like OTR or OpenPGP) is advanced and only for very advanced users in comparision to most common windows users.

So just a suggestion to do things right from the beginning

[COM8]

Yes, good point! Have to remember myself to keep it simple :D

[COM8]

That's the current state. Is this simple enough, what do you think?

[Echolon]

Hey - cool - I like it! Yes, now the user directly understands what it about. You should add the selection 'Unencrypted', too. Maybe a toggle thing is nice too.

And of course the lock symbol, but I guess it's work in progress.

(by Lock symbol I mean, you should offer those choices from this symbol, like in Dino or Conversations for example. But - sure - support choices with symbols, too!)

:raised_hands:

[Supded]

Fix fingerprint representation, it must be conversation capable.

[Supded]

[COM8]

Yes. I know what's going wrong and a fix will be published with the UI overhaul.

[COM8]

40d7a8b fixes it. Finally!

[stevenroose]

Is the progress list at the top still up to date? No encryption in MUCs yet?

[COM8]

Yes, still up to date since for MUC OMEMO support a few other bugs and milestones like:

• #50
• #55

have to be fixed/archived first.

[Neustradamus]

XEP-0384: OMEMO Encryption has been updated to 0.4.0 which breaks all:

• http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.3.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.4.0.html

[COM8]

Already created an Issue for it #126 . Thanks for the hint!

[Neustradamus]

XEP-0384: OMEMO Encryption has been updated to 0.4.0+:

• https://xmpp.org/extensions/xep-0384.html
• http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.6.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.7.0.html
• http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.5.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.6.0.html
• http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.4.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.5.0.html
• http://www.aptest.com/standards/htmldiff/htmldiff.pl?oldfile=https://xmpp.org/extensions/attic/xep-0384-0.3.0.html&newfile=https://xmpp.org/extensions/attic/xep-0384-0.4.0.html

PS : Not sure that 0.3.0 was complete before.

[closewall]

Any updates on this?

[COM8]

Sorry for the late response, but YES! UWPX now supports (OMEMO 0.7.0 (2020-09-05)) and I rewrote the complete OMEMO lib from the ground up. https://github.com/UWPX/UWPX-Client/releases/tag/v.0.31.0.0