-
-
Notifications
You must be signed in to change notification settings - Fork 224
Description
Me and my friend use the same version of profanity, we both have two OMEMO keys, one from another client and one created in profanity. When we do /omemo fingerprint <account> we only get the fingerprint of another client, but the profanity of the other is not listed.
But if we both do: /omemo fingerprint in the console, if the hash of profanity and that of the other client we use come out
I followed the steps detailed here: https://github.com/profanity-im/blog/blob/master/content/post/omemo.md , but it only lists one of the IDs of your mobile device but not that of your profanity client.
When we want to use Omemo and he writes to me from his profanity client I get this message: "You received a message encrypted with OMEMO but your client doesn't support OMEMO." ¯\_(ツ)_/¯
$ uname -a
OpenBSD 6.9 GENERIC#464 amd64
$ profanity --version
Profanity, version 0.10.0
Copyright (C) 2012 - 2019 James Booth <[email protected]>.
Copyright (C) 2019 - 2021 Michael Vetter <[email protected]>.
License GPLv3+: GNU GPL version 3 or later <https://www.gnu.org/licenses/gpl.html>
This is free software; you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Build information:
XMPP library: libmesode
Desktop notification support: Disabled
OTR support: Enabled (libotr 4.1.1)
PGP support: Enabled (libgpgme 1.15.1)
OMEMO support: Enabled
C plugins: Enabled
Python plugins: Enabled (3.8.8)
GTK icons: Disabled