dino icon indicating copy to clipboard operation
dino copied to clipboard

Allow to reset OMEMO keys

Open AltNico opened this issue 4 years ago • 5 comments

After restoring a slightly outdated backup, Dino fails in some conversations to decrypt messages. I suspect this is due to the key rotation of OMEMO which Dino can no longer follow.

You received a message encrypted with OMEMO but your client doesn't support OMEMO.

It would be cool if Dino offered to reset the OMEMO identity/keys, just like Conversations does under "Expert Settings" with the "Delete OMEMO identities" option.

In the meantime, is there any manual way to do this? Of course one could set up a Dino database from scratch, but all the history is then lost.

AltNico avatar Oct 19 '21 19:10 AltNico

Additionally, it sounds like Conversations has some self healing mechanism that would prevent issues like these. That's a different issue, though.

the OMEMO self healing mechanism introduced in 2.3.11

https://github.com/iNPUTmice/Conversations/blob/2.10.1/README.md#how-do-i-backup--move-conversations-to-a-new-device

AltNico avatar Oct 19 '21 19:10 AltNico

I have noticed this as well when the entire home directory was backed up and then restored after a reinstall. Though not just encrypted chats, but all chats seems broken. The chat list is shown, but all of them are empty - mam history fetch seems broken, not even new messages seems to come. I tried removing an account and adding again, but still the same error.

pravi avatar Apr 10 '24 05:04 pravi

I had to remove .local/share/dino and .config/dino and setup accounts again.

pravi avatar Apr 10 '24 10:04 pravi

Is there a way to do this without having to loose all chat history and the entire dino folder?

stevenroose avatar Sep 25 '24 19:09 stevenroose

It seems that removing the omemo.db file in your dino dir (~/.local/share/dino) works.

stevenroose avatar Sep 25 '24 19:09 stevenroose