You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 24, 2020. It is now read-only.
OMEMO encryption actually works for me. The issue is that I can't send encrypted messages until the person I want to talk with sent me an encrypted message, even though I already had encrypted conversations with them in the past.
Profanity command:
/omemo start contactX@some-jabber-server.org
// profanity output:
OMEMO Session started.
###############################################
# #
# CAUTION #
# This plugin does not support any form #
# of Trust Management #
# All Devices are trusted *blindly* #
# #
###############################################
// I send a message:
Last message was sent unencrypted.
me: hello
//contact sends me a encrypted message message (contact is actually me with a different account from my
phone running conversations)
contactX@some-jabber-server.org: hey!
me: NOW this message is encrypted.
Is this actually a limitation of profanity/omemo plugin, or is there some other issue?
$ profanity -v
Profanity, version 0.5.1
Copyright (C) 2012 - 2017 James Booth <boothj5web@gmail.com>.
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: Enabled
OTR support: Enabled
PGP support: Enabled
C plugins: Enabled
Python plugins: Enabled
GTK icons: Enabled