GPG issues with Kmail and, to a lesser extent, Alpine

harkonen · 09-04-2009, 11:26 AM

Slackware 13 64bit.

gnuPG worked well on 32bit 12.2 system, and I exported the keys with these commands:
bash$ gpg --armor --export > public.asc
bash$ gpg --armor --export-secret-keys > secret.asc
bash$ gpg --export-ownertrust > trustdb

Then I imported into slack13:
bash$ gpg --import public.asc private.asc
bash$ gpg --import-ownertrust trustdb

I set it as the key for signing and encrypting in Kmail and Pine and this is what happens:

Kmail:
error message == "Signing failed: Bad Passphrase"

Pine:
It does sign my messages successfully.
It does NOT encrypt, returning error: "Pipe command returned error. Hit return to continue."

Does any of this make sense to anyone? What am I doing wrong here? It feels like I'm not importing or exporting the keys correctly but I'm at a loss about what I need to do differently.

gegechris99 · 09-04-2009, 02:22 PM

Hello,

To setup GPG with KMail, please follow this KMail PGP_MIME HOW-TO.

In particular after the configuration of KMail, pay attention to the "Issues" section:

Quote:

To be sure the "passphrase agent" (gpg-agent) is enabled check your ~/.gnupg/gpg.conf and eventually uncomment the line containing "use-agent".

Quote:

* If you do not have it already, in ~/.kde create a directory called env. In there, create a file called gpgagent.sh containing

Code:

#!/bin/bash
killall gpg-agent
eval `gpg-agent --daemon`

Save it and make it executable.

In the same way you would clean up gpg-agent on shutdown, so if you do not have it already, create another directory called shutdown into ~/.kde and create in it another script file called stop_gpgagent.sh containing

Code:

#!/bin/bash
killall gpg-agent

Save it and make it executable.

It worked for me after I logout KDE and login again.

harkonen · 09-04-2009, 06:44 PM

Linuxquestions does it again. Amazing. Thanks, gegechris99 it worked like a charm. Brilliant. I'm adding that to my book of tricks.