Summary: | gpg does not work | ||
---|---|---|---|
Product: | [Applications] kmail2 | Reporter: | Daniel Moyne <daniel.moyne> |
Component: | crypto | Assignee: | kdepim bugs <kdepim-bugs> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | normal | CC: | sknauss |
Priority: | NOR | ||
Version: | 4.11.2 | ||
Target Milestone: | --- | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: |
gpg.conf
gpg-agent.conf |
Description
Daniel Moyne
2013-10-03 18:37:05 UTC
can you post ~/.gnupg/gpg.conf and ~/.gnupg/gpg-agent.conf ? Created attachment 82990 [details]
gpg.conf
Created attachment 82991 [details]
gpg-agent.conf
pinentry-qt4 workd whereas pinentry-kwallet does not
Sandro, have you found anything wrong? For the time being I am working without storing passphrases in KwalletManager. No I didn't found anything wrong with your gpg config. But actually you are using kubuntu, so there you don't need the /home/dmoyne/.kde/Autostart/start-gpg-agent.sh and should remove it. Do you know where you found the tip about creating this script? The agent will be started with XSession see /etc/X11/Xsession.d/90gpg-agent ( part of gnupg-agent package). If that doesn't help, than I'll have to look into the code of pinentry-kwallet. One question a little bit unrelated, why do you want to store the passphrase inside kwallet? For me it sounds like a big secure break. I know the gnupg guy really care about, where, when, what is written to RAM/Harddisk, so make it very difficult to get to the encrypted gnupg key. And I don't think this is true for kwallet. Yes Sandro regarding the use of a specific script in /home/dmoyne/.kde/Autostart/start-gpg-agent.sh It seems useless as it is trated where you say I will remove it. Now I have also a script to shut it down in .kde/shutdown What do I do with it? All these scripts were proposed at one time on internet. Now apparently they are uncecessary. The idea to use kwallet to store the passphrase is documented in gpg doc somewhere and I find it comfortable to be avoid answering the pasphrase question that is all. I would also delete the shutdown script too and test if gpg-anget is killed with the end of the session. Actually this additional start-gpg-agent.sh script start an additional gpg-agent, that can problems :) Like one programm connets to one agent the other to the other. So please make sure, when trying pinentry-kwallet again, that only one gpg-agent is running. Sandro after removing all scripts if I set in"gpg-agent.conf": pinentry-program /usr/bin/pinentry-kwallet it is still hanging after kwallwallet question for password. Therefore I still think that the problem is in the way the passphrase is stored in kwallet and retrieved from kwallet I search today around and saw, that pinentry-kwallet is not part of KDE. It is developed by MirBSD (Thorsten Glaser <tg@mirbsd.org>). The code of pinentry-kwallet hasn't changed since 2012, so maybe the kwallet protocoll has changed. The best would be to send this bugreport to Thorsten. Please add a bugnumbers, if you creates bugreports at other project. Thanks Sando I will ty to liaise with Thorsten Glaser if the e-mail is still correct and keep you posted in case he answers anything. This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months. Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input. |