-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There was an error decrypting an OMEMO message addressed to this device. See the debug log for details. #186
Comments
Another system now has the same problem. |
Hi @ZenithElevate, thanks for the report. Regarding the output from the log: Did you put the dots in the keys? If not, this is invalid base64 encoding. |
No, those libraries have been copied onto each of the machines, from the same location, and never touched since. |
Are you able to confirm whether it is the expected behavior that a few weeks since the activation lurch begins to send corrupted messages? |
That is certainly not expected behaviour. One other moving part is the XMPP server. Were there any upgrades/restarts? If the server can't keep the PEP node state right, as has happened in the past, things can get weird. |
Where does lurch keep its keys? |
There is a per-user sqlite DB. A decryption error is not necessarily related to the key material however, it could simply be failing at the XML parsing step. |
Reciver:
Sender:
|
That error code seems pretty bad, it's deep from inside |
Receive:
Send:
|
In my infrastructure, there is a bunch of Pidgin clients on Windows, a bunch of Android phones with Conversation, and my one and only Linux with Pidgin. Some time ago, I migrated all of them from OTR to OMEMO, and everything worked well until a couple days ago when one and only one Windows Pidgin began to fail to deliver messages to my Linux Pidgin.
I can send to it fine. When it sends to me I get:
This is what corresponds to that error in debug log:
Pidgin folks don't know what Lurch does, so the question is to you how is it possible that only one way communication suddenly broke from only one client, and how to restore service?
The text was updated successfully, but these errors were encountered: