Bug 317358 - sending signed messages with gpg no more works
Summary: sending signed messages with gpg no more works
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail2
Classification: Applications
Component: general (show other bugs)
Version: 4.10.1
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2013-03-25 23:05 UTC by Daniel Moyne
Modified: 2018-10-27 02:07 UTC (History)
1 user (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 Daniel Moyne 2013-03-25 23:05:24 UTC
since today sending signed mail or cryped massages with a key no more works : bad pass phrase (stored in kwallet)
Comment 1 Daniel Moyne 2013-03-25 23:14:38 UTC
it looks like this bug is related to a boot with the latest proposed kernel 3.8.0-14-generic. No problems with kernel 3.8.0-13-generic.
Comment 2 Sandro Knauß 2013-09-19 22:29:08 UTC
Can you tell more inforamtions - what kind of key you use? Is the bug still present?
Comment 3 Daniel Moyne 2013-10-06 12:03:28 UTC
I am using keys that worked before built with the normal procedure with :
gpgsm --gen-key

and anyways it is not a problem of keys as as explained in my bug report if I do this in a konsole :
eval "`gpg-agent --daemon`"
kmail
it works and without asking for anything.

But if I use the normal way with, when opening a KDE session, execution of the following script "start-gpg-agent.sh" located in "/home/my_user/.kde/Autostart" and containing this :
#!/bin/sh
eval "`gpg-agent --daemon`"
it does not work when trying to send a signed message. The first time it opens a window  saying that KWallet CLI has requested to open kdewallet. When I follow the procedure nothing happens: the message is never sent.

The question is for me as user what is the difference between konsole procedure asking for nothing and the normal one when after opening my kde session I use kmail?

What is more surprising is that if I open a konsole right after opening my KDE session if I do :
echo $GPG_AGENT_INFO
I get someting like this :
/tmp/gpg-hywGcN/S.gpg-agent:3873:1
but if I open Kmail in this konsole sending a signed message does not work. I all cases in my konsole I have to do :
eval "`gpg-agent --daemon`"
each time before executing kmail.

This configuration problem arose when I migrated from kubuntu 13.04 to 13.10
Comment 4 Daniel Moyne 2013-10-19 15:03:18 UTC
if I replace pine-entry-kwallet by pine-entry-qt4 it works fine but of course it does ask for the pass phrase each time. I think the problem is with pine-entry-kwallet that does not properly store information and threfore when sending a signed message the pass phrase cannot be retrieved. How can I test the way the information is stored in kwallet for each new key?
Comment 5 Sandro Knauß 2013-10-19 20:33:28 UTC
pine-entry-kwallet? this is a programm i don't know. On my system there are only:
pinentry-curses
pinentry-x11
pinentry-qt
pinentry-doc
pinentry-gtk2
pinentry-x2go
pinentry-qt4 (*installed)
pinentry-gtk

To not enter the password not every time gpg-agent is used see .gnupg/gpg-agent.conf

  pinentry-program /usr/bin/pinentry-qt4
  default-cache-ttl 1800

^^default-cache-ttl Set the time a cache entry is valid to n seconds.  The default is 600 seconds.

You use SMIME Keys, right?
Comment 6 Daniel Moyne 2013-10-20 07:59:28 UTC
pineentry-kwallet is a program included in kwalletcli allowing to set and getr passwords in th default KDE wallet (kwalletmanager). Once th KWallet is activated once by a password, all passwords will be retrieved from it like for accessing a protected bak site, pop mail, etc... You no more have to answer the passphrase each time when sending a signed message.

You said "You use SMIME Keys, right?"
Sandro how can I verify this?
Comment 7 Andrew Crouthamel 2018-09-25 03:50:43 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 8 Andrew Crouthamel 2018-10-27 02:07:57 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!