Seems not to encrypt correctly

[mase76]

Hi! When sending a message to an android device with conversations, the android user is told, that the message cannot be decrypted, because the private key is missing. But the key-id displayed in pidgin is correct. Receiving a message from conversations in pidgin works as it should. Also the key is not found on the keyservers when searching from within pidgin.

[github-k8n]

This is identical to issue #11

[mase76]

No, this is not a carbon related issue. Messages from Pidgin to Conversations cannot be decrypted at all.

[github-k8n]

Question: Is the xmpp user on Pidgin and Conversations the same?

If yes, then it is a Carbon Copy issue.

If no, then please verify that you have the correct key in the gpg keyring in pidgin (of which the PRIVATE part is available in Andoid OpenKeyring. You could attach the public keys of both users AND the message sent from pidgin (get it from the debug console) so we could find out if it is correctly encrypted.

[mase76]

No, the user isn't the same. It's a normal chat. The debug window tells me the correct key-id being used. Pidgin to Pidgin works as it should. Maybe it isn't a Pidgin-GPG issue. The recepient is prompted to unlock his gpg key in Conversations. Openkeychain is used. After that he is told, that the message cannot be decrypted, because he does not have the correct private key. And this happens for both parties.

I also wonder, that the key cannot be found on the keyserver from within pidgin. However I already have the key on my keyring.

BTW: I haven't the carbon feature. I use an openfire server, which does not have a carbon plugin (at the moment).

[github-k8n]

You would need to look at the sent message (the ciphertext) with gpg to see which public key was actually used for encryption on the sender's side. Then you can compare that to the private key that is available at the recipient side.

I can verify that OpenPGP encryption in general is working fine with pidgin (on linux/gentoo) and conversations. (using Prosody as server)

[mase76]

As I said: Pidgin to Pidgin works Conversations to Pidgin works Pidgin to Conversations does not work Conversations to Conversations works So I am sure, that the correct pubkey was used. I cannot see the cipher text in Conversations to verify.

[github-k8n]

From your description it looks like you have the wrong private key in Android. You could get the message ciphertext/source in pidgin when sending (not in Conversation when receiving...)

[mase76]

I double checked the keys on all clients. In Conversations' contact details I see the correct public key being used to encrypt. and the recepient has the correct private key in Openkeychain. Also in Pidgin. Why is the recepient asked to unlock his private key and after unlocking he is told, that the key is missing? And that on both sides. Where do you see the cipher text in Pidgin? In the debug console?

[github-k8n]

Yes, in the debug window, select "All" and you should see something like: "jabber: Sending (ssl) " with the actual XML message being sent.

[mase76]

Cannot open it in gpg. I have only one private key in Android. I also use it for email without problems. So I am sure, I have the correct private key in Openkeychain.

[github-k8n]

Just paste it here

[github-k8n]

It is encrypted to these two keys: keyid 3EA6782B27E2EA33 keyid 0FCEB09C2D65E644

Can you check the key id for your private key in OpenKeychain?

[mase76]

Both are the correct subkeys. One is mine, one is the recepient.

[mase76]

For whatever reason, my topkey was also marked for encryption. Created a new keypair, everything works now.