Cannot receive PGP-encrypted messages.
50 views
Skip to first unread message
Matthew Wynn
Mar 19, 2016, 1:14:44 AM3/19/16
to profanity development
Hi, I'm running profanity 0.4.7 on Void Linux with PGP support enabled. I've set the pgpkeyid on my account, and the key of some of my contacts, and I can send encrypted message just fine. However, whenever I receive an encrypted message, it simply says "This is an XEP-0027 encrypted message" or "[This message is *encrypted* (See :XEP:`27`]." The PGP status on the top simply says "PGP send," never recv. I have verified that this key works fine in Gajim, but it's not working in Profanity. Any help on getting Profanity to decrypt would be appreciated, as I would like to use this as my main XMPP client.
Thanks,
Matthew
Thanks,
Matthew
Boothj5
Mar 21, 2016, 5:59:11 AM3/21/16
to profanity development
Just to double check:
* The "PGP Key ID" appears in /account show <account>, and matches one of those listed with /pgp keys as PUBLIC/PRIVATE
* The contact is listed in /pgp contacts, with a key marked as PUBLIC in /pgp keys
If these are correct I'm not sure why the messages are not being decrypted and will have to try to recreate.
If these are correct I'm not sure why the messages are not being decrypted and will have to try to recreate.
Matthew Wynn
Mar 21, 2016, 6:06:04 PM3/21/16
to profanity development
Boothj5,
I can confirm that both of those are correct on my system.
I did some more testing. My problem seems to only occur if I have both Profanity and Gajim open. If I close Gajim, Profanity switches to PGP send/recv on the next incoming message and works fine from there. I don't know which program is at fault here. I was under the impression that both supported carbons. I suppose this works, though.
I can confirm that both of those are correct on my system.
I did some more testing. My problem seems to only occur if I have both Profanity and Gajim open. If I close Gajim, Profanity switches to PGP send/recv on the next incoming message and works fine from there. I don't know which program is at fault here. I was under the impression that both supported carbons. I suppose this works, though.
Boothj5
Mar 21, 2016, 6:29:43 PM3/21/16
to profanity development
Thanks for the extra info, I wasn't aware you had carbons enabled.
I think this is most likely a bug in profanity, not decrypting carbons. I'll take a look to verify this, add a fix as soon as possible, and update this post.
I think this is most likely a bug in profanity, not decrypting carbons. I'll take a look to verify this, add a fix as soon as possible, and update this post.
Boothj5
Mar 21, 2016, 8:38:15 PM3/21/16
to profanity development
Recreated the issue and have added a fix in master. Both incoming and outgoing carbons are now decrypted.
It'll be in the next release, but if you want to build and test from master, instructions for a manual install are at: http://www.profanity.im/install.html#manualinstall
Two additional dependencies required:
autoconf-archive
libtool
It'll be in the next release, but if you want to build and test from master, instructions for a manual install are at: http://www.profanity.im/install.html#manualinstall
Two additional dependencies required:
autoconf-archive
libtool
Boothj5
Mar 28, 2016, 8:19:01 PM3/28/16
to profanity development
Issue logged at: https://github.com/boothj5/profanity/issues/775
Currently only the incoming carbon can be decrypted by the receiver, the outgoing carbon can't be decrypted by the sender since they don't have the receivers private key. This appeared to work when testing, but this was because testing was done on one machine where the key store contains all keys.
Currently only the incoming carbon can be decrypted by the receiver, the outgoing carbon can't be decrypted by the sender since they don't have the receivers private key. This appeared to work when testing, but this was because testing was done on one machine where the key store contains all keys.
Reply all
Reply to author
Forward
0 new messages