support for OMEMO encryption #529

georgehazan · 2016-10-22T16:02:10Z

Reported by plahh on 10 Feb 2016 15:41 UTC
as requested in this thread
here is the ticket :)

http://conversations.im/omemo/
https://en.wikipedia.org/wiki/OMEMO_%28encryption%29

gajim already got a plugin. code here

georgehazan · 2016-10-22T16:02:10Z

Comment by sss_sss on 8 Sep 2016 20:17 UTC
i am on it

georgehazan · 2016-10-22T16:02:18Z

Comment by sss_sss on 24 Sep 2016 06:08 UTC
нужно больше золота....

LittleVulpix · 2017-02-22T14:57:23Z

@sss123next , tagging you with this ticket since you said you are now working on it. :)

dreamflasher · 2017-06-12T12:35:16Z

@georgehazan @sss123next Is there any status update for us? :)

georgehazan · 2017-06-12T17:21:21Z

doesn't it work? in the dev version, of course

sergeevabc · 2017-06-13T11:42:18Z

Do you believe current implementation with the following todo is cooked enough to be used in production?

TODO:

fix AES-128 GCM in 4.5 implementation

handle prekeys properly (cleanup after first use, create new keys)

reimplement session initialization without loosing first message (incomming + outgoing)

fingerprints/keys management ui

per-contact encryption settings (enable/disable for one contact)

georgehazan · 2017-06-13T14:56:32Z

you better ask @sss123next about it

dreamflasher · 2017-06-14T20:47:23Z

@georgehazan No it doesn't. I found this thread where he apparently writes updates: http://forum.miranda-ng.org/index.php?topic=4506.30 -- but how exactly am I supposed to retrieve the plugin with his commits? It is said somewhere that it's supposed to be in "dev" Miranda, but there is apparently currently none: http://www.miranda-im.org/development/
I have the latest Miranda, with the latest jabber plugin and I don't see any possibility to use Omemo.

LittleVulpix · 2017-06-14T22:44:13Z

@dreamflasher That's MirandaIM which is pretty dead. This is miranda NG where the changes are taking place. Get the latest dev version from here: http://www.miranda-ng.org/en/downloads/ , if you want to migrate from IM to NG, there is a nice article on our wiki. Make sure to backup everything beforehand.

dreamflasher · 2017-06-15T15:47:51Z

@LittleVulpix Ah bummer! I first tried with Miranda NG, but it didn't work there, so then I tried Miranda. I have switched to Miranda NG a while ago, but when I now checked
http://www.miranda-ng.org/en/downloads/ "17.6.2016 New stable build released, 0.95.5"
http://www.miranda-im.org/ "Miranda IM v0.10.70 Released June 06, 2017"
So I thought Miranda would be more current than Miranda NG again.
But yeah, same with me for Miranda NG: I have the development version from the place you wrote, and Omemo doesn't work. I have a chat with Omemo on conversations/gajim, and I don't get the messages on Miranda, also Miranda doesn't announce itself as Omemo capable. How do I activate it? Is there any manual anywhere?

LittleVulpix · 2017-06-15T15:51:57Z

@dreamflasher

Yes, there is a way to toggle it on. As long as you are on the dev version of miranda, go to main miranda options menu, type network into the search box, find the name of the network you want to modify (the internal name you gave it, probably jabber if you haven't changed anything), go into advanced and scroll at the very bottom - there is an option to enable Omemo.

And yeah, there hasn't been a stable release in a while - but the dev branch is safe for the most part.

See screencap from my miranda:

dreamflasher · 2017-06-15T16:00:22Z

@LittleVulpix Thank you very much! I was able to active it (although activating crashed Miranda NG).
Then I tried do start a conversation with an Omemo contact, it asks to create a new session, but the messages aren't received by the other end. Also new messages aren't received by Miranda NG.

LittleVulpix · 2017-06-15T16:29:49Z

@dreamflasher Ahh, I don't use Omemo myself, so I never tested it. I guess this is a question for @sss123next since he is developing the omemo plugin. Sorry it didn't work! :(

dreamflasher · 2017-06-15T16:31:13Z

@LittleVulpix You were very helpful in setting things up, so thank you very much for that!
Maybe @sss123next can take over with the bugs? :)

sss123next · 2017-06-20T23:31:10Z

hmm.
i have tested it with success.
one thing which is not done properly yet - is aes128gcm tagging (verification always fail in my case), but actual encryption/decryption work fine.
other TODO entries is convenience mostly, not XEP implementation related.
i will recheck it.
crashes are completely unexpected behavior.
i will investigate it.

sss123next · 2017-06-21T00:03:27Z

i have done quick tests. all looks normal screenshot . so i need more info. check miranda console, it may have useful readable debug messages, also check xml console, i am also need crashlogs, backtraces e.t.c. in case of crash.

I did not use the Miranda plugin but looking at their discussion, it seems they have a working version already miranda-ng/miranda-ng#529

wiktor-k · 2017-08-01T12:18:20Z

I'm getting Delivery failure: No valid OMEMO session exists when sending a message to OMEMO-enabled contact. Are there any other options/actions besides Network/Advanced/Use OMEMO?

I'm using stock Miranda NG 0.95.6 64bit.

wiktor-k · 2017-10-27T12:46:50Z

@sss123next I downloaded the version from https://www.miranda-ng.org/distr/miranda-ng-alpha-latest_x64.7z

Unfortunately the error still exists (Delivery failure: No valid OMEMO session exists). Plugins page shows jabber.dll version 0.11.0.5. Is it possible that this is related to contact using Prosody that does not persist PubSub items (so that keys could be removed after restart)?

Do I need to create new profile from scratch or should the update (overwrite all files) take care of everything?

dryo · 2017-10-27T13:16:25Z

I too have Problems: I'm sending messages but the other party does not receive/see them. When the other party sends me a message I get this:

I sent you an OMEMO encrypted message but your client doesn’t seem to support that. Find more information on https://conversations.im/omemo

The receiving end uses conversations and I had an OMEMO encrypted session also with conversations with the receiver earlier. The receiver probably did not close the app in the meantime. Maybe this is relevant.

Network log says this when receiving:

[14:57:59 1F90] [***@***] Inflate: Z_OK
[14:57:59 1F90] [***@***] (ZLIB) Data received
<message to='***@***/***' from='***@***/mobile' type='chat' id='757eb832-6ec9-4490-9871-c423c84b27ae'><encrypted xmlns='eu.siacs.conversations.axolotl'><header sid='1511459254'><key prekey='true' rid='214083405'>MwhhEiEF3lJUNCjrDBXi3Ghv0goXqOMtET9gISTo6zv9QujIMgUaIQXd3hQ3L/wRegQTlMS3Sj3nPpz+S/8VjYtn7scY33AeXCJiMwohBT5RTQ+yJojmHKzvZPCykiGDZ7hzuoydd6YwYQwL/KVPEAEYACIwVtj2AxqtDdMMD4oY/ehMBqXs7E+vqD0POVkIaD0U89N9Gpz7gFLRWAGhUgHWs4MWWnMNihctiYAotpPc0AUwAQ==</key><iv>DF6SuD6N2G8uJnAC9CmA6w==</iv></header><payload>Zvg8vGSHLo5vUz/XmZudUsoR3WjJHg8f+hbJnmx6twmGf4QguyDHdimJWbt4YQ==</payload></encrypted><markable xmlns='urn:xmpp:chat-markers:0'/><origin-id xmlns='urn:xmpp:sid:0' id='757eb832-6ec9-4490-9871-c423c84b27ae'/><store xmlns='urn:xmpp:hints'/><encryption xmlns='urn:xmpp:eme:0' namespace='eu.siacs.conversations.axolotl' name='OMEMO'/><body>I sent you an OMEMO encrypted message but your client doesn’t seem to support that. Find more information on https://conversations.**/omemo</body></message>
===IN: 1022(223) bytes
[14:57:59 1F90] [***@***] recvResult = 1022
[14:57:59 1F90] [***@***] bytesParsed = 1022
[14:58:00 1F90] [***@***] Jabber OMEMO: error: session_cipher_decrypt_pre_key_signal_message failed SG_ERR_INVALID_MESSAGE
[14:58:00 1F90] [***@***] Jabber OMEMO: error: signal_message_deserialize failed with unknown error
[14:58:00 1F90] [***@***] Jabber OMEMO: error: failed to decrypt incomming message
[14:58:00 1F90] [***@***] JabberUpdateMirVer: for jid ***@***
[14:58:00 1F90] [***@***] JabberUpdateMirVer: for rc mobile: http://conversations.im#+wL56uyy89dgaGVTbnJJpkXpkIE=

Network log says this when sending:

[14:58:24 2030] [***@***] Deflate: Z_OK
[14:58:24 2030] [***@***] (ZLIB) Data sent
<message to="***@***/mobile" id="mir_28"><encrypted xmlns="eu.siacs.conversations.axolotl"><payload>kOapO3NhnifBOhSY</payload><header sid="214083405"><key rid="1511459254">MwjXHRIhBS2BelDPQ2hlaDe0pF2NYtkoE7H17DoGRXpSJxtFYVE7GiEFQqbmCQumd156Dnr7dHYsuqOPJfN8oFlkbmOSmK6gfkEiUjMKIQUWt0mm7Zrsxhj+zvockZZ5GHImMA9Fzrd7axiysD/DAhABGAAiIM3Wd/o69zoLalxhdN3Jj3A6QppAtkoQQm6t7SEhW8VIIvOUDyzr5mgozc6KZjAm</key><iv>9O0GUHl+PRYnnXir</iv></header></encrypted><store xmlns="urn:xmpp:hints"/><active xmlns="http://jabber.org/protocol/chatstates"/></message>
===OUT: 544(115) bytes
[14:58:24 11B4] [***@***] Broadcast ACK
[14:58:24 11B4] [***@***] Returning from thread

dryo · 2017-10-27T14:33:48Z

Addition: Also when enabling or disabling OMEMO in settings while being connected miranda crashes. Care for crash reports?

sss123next · 2017-11-27T03:24:14Z

sorry for delay

Unfortunately the error still exists (Delivery failure: No valid OMEMO session exists). Plugins page shows jabber.dll version 0.11.0.5. Is it possible that this is related to contact using Prosody that does not persist PubSub items (so that keys could be removed after restart)?

xml log from miranda will be helpful

Do I need to create new profile from scratch or should the update (overwrite all files) take care of everything?

all should be done automatically, but you can manually remove all omemo* in database in jabber section to be sure

The receiving end uses conversations and I had an OMEMO encrypted session also with conversations with the receiver earlier. The receiver probably did not close the app in the meantime. Maybe this is relevant.

Network log says this when receiving:

https://xmpp.org/extensions/xep-0384.html#namespaces - they broke it again...
i will rollback in next few days.

Addition: Also when enabling or disabling OMEMO in settings while being connected miranda crashes. Care for crash reports?

yes.

so, for now post crashlogs, and wait for namespace rollback, also i will reread xep again, maybe they have broke something more than this..

sss123next · 2017-11-27T17:52:58Z

51e27d7 - rollback to "updated" https://xmpp.org/extensions/xep-0384.html

this should resolve incompatibility with fresh implementations (also this will break compatibility with others once more)

dartraiden · 2018-03-26T18:16:48Z

#1215
after crash and start, OMEMO enabled in settings, but I receive

I sent you an OMEMO encrypted message but your client doesn’t seem to support that. Find more information on https://conversations.im/omemo

from contact

sss123next · 2018-03-26T21:16:15Z

i need xml logs.
better from both sides if possible.

sss123next · 2018-04-09T03:26:16Z

look on #1255 for further development

sss123next · 2018-04-24T10:02:15Z

current implementation is incompatible with conversation for some reason.
we constantly have SG_ERR_INVALID_MESSAGE on attempt to do session_cipher_decrypt_pre_key_signal_message on incoming prekey message from conversations

and no info on conversations side ( looks like conversations does not have any debugging at all.... )

i have redone tests with miranda<>miranda, it works.
i have done all tests with latest libsignal-protocol-c.

Neustradamus · 2019-09-06T08:09:20Z

OMEMO 100% works with Miranda NG?

OmlineEditor · 2019-10-22T15:20:12Z

Not 100% implemented OMEMO :-(
interface not yet finalized.
Is there a graphical menu where you can see and verify the keys?
I do not see the interface for normal operation.

RIS2000 · 2019-10-25T11:46:07Z

Still no success Miranda <-> Conversations. But Gajim works pretty well, so i suppose that Miranda have some faulty implementation ((

tigexplorer · 2019-12-14T16:16:59Z

I've no success with Miranda <-> Conversations and Miranda <-> Dino

Neustradamus · 2021-02-15T14:07:00Z

@LittleVulpix, @sergeevabc, @dreamflasher, @wiktor-k, @dryo, @dartraiden, @Duke690, @OmlineEditor, @RIS2000, @tigexplorer, @gjf: Can you test the last upstream code?

@sss123next has done some changes yesterday.

The goal is to have a perfect XEP-0384 0.3.0 version:

XEP-0384: OMEMO Encryption 0.3.0 #2719

gjf · 2021-02-16T11:22:15Z

@Neustradamus OMEMO still does not work with Conversations.
Psi+ does.

ageis · 2021-04-29T10:17:53Z

Will be eagerly tracking this.

a11cf0 · 2024-02-07T13:37:38Z

Still doesn't seem to work with Conversations.

dreamflasher · 2024-02-07T14:17:54Z

I switched to beeper, which wowed me from a user experience perspective.

Neustradamus · 2024-02-07T14:28:44Z

@georgehazan, @sss123next: Can you look this problem please?
Thanks in advance.

sss123next · 2024-02-07T15:26:17Z

i will check in few days.

OmlineEditor · 2024-02-08T12:05:20Z

OMEMO encryption works well between:
Maranda v0.96.4 #26381 and Conversations on Android v2.12.6 (old version)
Maranda v0.96.4 #26381 and Conversations on Android v2.13.0 (new version)
Maranda v0.96.4 #26381 and Blabber.im v3.1.4 (analogue Conversations)

I do not know exactly what encryption algorithms are used there, but everything seems to work.

perhaps the problem is changing the keys in the MEMO and Miranda does not understand well that the keys need to be used by others. I had a similar problem when there were several encryption keys and some of them were not used. for Miranda, you need to hand over the ability to delete and revoke your old keys from the server.

Neustradamus · 2024-02-08T12:29:56Z

@OmlineEditor: For information, there is a problem in Metronome IM but it is not the problem with Miranda NG:

Missing PEP/PubSub feature announcement maranda/metronome#549

Please, can you edit your last message?
Maranda -> Miranda NG
MEMO -> OMEMO

Note there is OMEMO 0.3.0 and the new OMEMO...

sss123next · 2024-02-22T22:51:41Z

georgehazan added another plugin major T: task enhancement Jabber and removed T: task another plugin labels Oct 22, 2016

georgehazan added trivial and removed major labels Oct 22, 2016

dartraiden assigned sss123next Feb 22, 2017

gjedeer added a commit to gjedeer/omemo-top that referenced this issue Jul 19, 2017

Update miranda_ng.yml

bdabb67

I did not use the Miranda plugin but looking at their discussion, it seems they have a working version already miranda-ng/miranda-ng#529

gjedeer mentioned this issue Jul 19, 2017

Update miranda_ng.yml bascht/omemo-top#68

Merged

bascht pushed a commit to bascht/omemo-top that referenced this issue Jul 19, 2017

Update miranda_ng.yml

b8c4010

I did not use the Miranda plugin but looking at their discussion, it seems they have a working version already miranda-ng/miranda-ng#529

bascht mentioned this issue Feb 9, 2018

Add Miranda-IM client bascht/omemo-top#93

Merged

sss123next closed this as completed Apr 9, 2018

sss123next reopened this Apr 24, 2018

sss123next closed this as completed in 31de2bb Apr 27, 2018

Duke690 mentioned this issue Jun 11, 2018

Ejabberd OMEMO #1417

Closed

gjf mentioned this issue Feb 13, 2021

New_GPG: implement existing keys detection #2728

Closed

sss123next mentioned this issue Feb 21, 2021

omemo broken (regression) #2750

Closed

support for OMEMO encryption #529

support for OMEMO encryption #529

Comments

georgehazan commented Oct 22, 2016 • edited by dartraiden Loading

georgehazan commented Oct 22, 2016

georgehazan commented Oct 22, 2016 • edited by dartraiden Loading

LittleVulpix commented Feb 22, 2017

dreamflasher commented Jun 12, 2017 • edited Loading

georgehazan commented Jun 12, 2017 • edited Loading

sergeevabc commented Jun 13, 2017

georgehazan commented Jun 13, 2017

dreamflasher commented Jun 14, 2017

LittleVulpix commented Jun 14, 2017

dreamflasher commented Jun 15, 2017

LittleVulpix commented Jun 15, 2017 • edited Loading

dreamflasher commented Jun 15, 2017

LittleVulpix commented Jun 15, 2017

dreamflasher commented Jun 15, 2017

sss123next commented Jun 20, 2017 • edited Loading

sss123next commented Jun 21, 2017

wiktor-k commented Aug 1, 2017

wiktor-k commented Oct 27, 2017

dryo commented Oct 27, 2017 • edited Loading

dryo commented Oct 27, 2017

sss123next commented Nov 27, 2017 • edited Loading

sss123next commented Nov 27, 2017 • edited Loading

dartraiden commented Mar 26, 2018 • edited Loading

sss123next commented Mar 26, 2018 • edited Loading

sss123next commented Apr 9, 2018

sss123next commented Apr 24, 2018 • edited Loading

Neustradamus commented Sep 6, 2019

OmlineEditor commented Oct 22, 2019

RIS2000 commented Oct 25, 2019

tigexplorer commented Dec 14, 2019 • edited Loading

Neustradamus commented Feb 15, 2021

gjf commented Feb 16, 2021

ageis commented Apr 29, 2021

a11cf0 commented Feb 7, 2024

dreamflasher commented Feb 7, 2024

Neustradamus commented Feb 7, 2024

sss123next commented Feb 7, 2024

OmlineEditor commented Feb 8, 2024 • edited Loading

Neustradamus commented Feb 8, 2024

sss123next commented Feb 22, 2024

georgehazan commented Oct 22, 2016 •

edited by dartraiden

Loading

georgehazan commented Oct 22, 2016 •

edited by dartraiden

Loading

dreamflasher commented Jun 12, 2017 •

edited

Loading

georgehazan commented Jun 12, 2017 •

edited

Loading

LittleVulpix commented Jun 15, 2017 •

edited

Loading

sss123next commented Jun 20, 2017 •

edited

Loading

dryo commented Oct 27, 2017 •

edited

Loading

sss123next commented Nov 27, 2017 •

edited

Loading

sss123next commented Nov 27, 2017 •

edited

Loading

dartraiden commented Mar 26, 2018 •

edited

Loading

sss123next commented Mar 26, 2018 •

edited

Loading

sss123next commented Apr 24, 2018 •

edited

Loading

tigexplorer commented Dec 14, 2019 •

edited

Loading

OmlineEditor commented Feb 8, 2024 •

edited

Loading