Bug 115310 - "encrypted mail" "too many passphase" requests
Summary: "encrypted mail" "too many passphase" requests
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: encryption (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2005-10-29 12:18 UTC by Andrew Bird
Modified: 2015-04-12 10:16 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Bird 2005-10-29 12:18:29 UTC
Version:            (using KDE KDE 3.4.2)
Installed from:    Fedora RPMs
OS:                Linux

After enabling gpg-agent, setting its 
default-cache-ttl 86400
max-cache-ttl 86400
and restarting everything, kmail still prompts me too often for the passphrase to unlock my own key. 
It asked once for a new mail received, once for a compose and also other occasions which I don't seem to be able to relate to an event. Surely, once I've provided the passphrase for my key, it should not ask again unless gpg-agent says the cache has expired.
Comment 1 Jaime Torres 2008-09-18 09:44:58 UTC
Within kmail 1.10.1, expire cached PINs after N seconds is set to 600 seconds, with kwallet enabled, it never asked me the passphrase. 
Comment 2 Michael Leupold 2009-04-04 20:00:34 UTC
My cache seems to work fine. Is this still an issue or can we close this bug?
Comment 3 Andrew Bird 2009-04-05 11:13:10 UTC
Hi this bug was seen when kwallet was not in use. I no longer have the system I saw the problem on. I now have switched to using kwallet because of this type of annoyance since it hides all of these types of issues. You may close it since it is no longer a problem to me, but you may want to confirm that it's not a problem when not using kwallet first.
Comment 4 Laurent Montel 2015-04-12 10:16:20 UTC
Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.