By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.
Bug 630 - KMail issue with gpg keys
Summary: KMail issue with gpg keys
Status: NEW
Alias: None
Product: TDE
Classification: Unclassified
Component: tdepim (show other bugs)
Version: 3.5.13.x [Trinity]
Hardware: amd64 Debian Squeeze
: P5 normal
Assignee: Timothy Pearson
URL:
Depends on:
Blocks:
 
Reported: 2011-11-16 12:49 CST by Kris
Modified: 2018-05-27 11:10 CDT (History)
2 users (show)

See Also:
Compiler Version:
TDE Version String: 3.5.13
Application Version: 1.9.10
Application Name: Kmail

Attachments
Screenshot of the kmail add-key dialog, showing the issue as described (171.90 KB, image/png)
2011-11-16 12:49 CST, Kris 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kris 2011-11-16 12:49:12 CST 
Created attachment 129 [details]
Screenshot of the kmail add-key dialog, showing the issue as described

When attempting to add a gpg key to Kmail for signing and/or encrypting, Kmail grays out the OK button and displays a question mark next to each key it recognizes.
Comment 1 Kris 2011-11-16 12:55:50 CST 
If I open ~/.trinity/share/config/emailidentities and add the key fingerprint to "PGP Encryption Key=" and "PGP Signing Key=", Kmail recognizes the key as valid and both signing and encryption work.

In my ~/.gnupg/gpg.conf, use-agent is added.

KGPG is loaded and sitting in my system tray.

I have tried with gpg-agent running as a daemon, and without it running as a daemon. I turn on the Use Agent setting in KGPG when gpg-agent is running, and turn off the setting when gpg-agent is off, it didn't work in either case.

I currently am able to use my key using the emailidentities workaround without gpg-agent, but KGPG is still running.
Comment 2 Kris 2012-09-30 19:40:25 CDT 
(In reply to comment #1)
> If I open ~/.trinity/share/config/emailidentities and add the key fingerprint
> to "PGP Encryption Key=" and "PGP Signing Key=", Kmail recognizes the key as
> valid and both signing and encryption work.
> 
> In my ~/.gnupg/gpg.conf, use-agent is added.
> 
> KGPG is loaded and sitting in my system tray.
> 
> I have tried with gpg-agent running as a daemon, and without it running as a
> daemon. I turn on the Use Agent setting in KGPG when gpg-agent is running, and
> turn off the setting when gpg-agent is off, it didn't work in either case.
> 
> I currently am able to use my key using the emailidentities workaround without
> gpg-agent, but KGPG is still running.

I should add that it doesn't matter whether or not KGPG is open, signing and encrypting work with or without it, provided I use the workaround.
Comment 3 deloptes 2016-05-20 16:12:59 CDT 
I stumbled upon this bug and want to add here that this was always the behavior of kmail. However if the key is signed and trusted (green in kgpg) it is accepted.
After this it appears in the ~/.trinity/share/config/emailidentities file.
I wouldn't say this is a bug
Comment 4 deloptes 2017-08-01 15:17:51 CDT 
after looking into the code this goes to libgpgme and not to kgpg - at least I have not seen anything there to do with kgpg . This would explain why use gpg-agent did not take effect from KMail perspective.
Comment 5 deloptes 2017-08-14 14:56:43 CDT 
Something else come to my mind lately.

the library libgpgme as well as the gnupg agent are meant to cache passwords in secure way, so despite of the fact that there was confusion what is responsible for what in the mail signing process and not really likely to include the requested functionality, I was wondering what is the benefit of your suggestion, also, if libgpgme does not use gnupg, it would ask for password each and every time.

I'm just pleading to close old issues and requests :)