[prev in list] [next in list] [prev in thread] [next in thread]
List: kmail-devel
Subject: [Bug 136676] Kmail doesn't ask for passphrase for GPG signed message
From: dAniel hAhler <kde-bugzilla () thequod ! de>
Date: 2007-06-07 0:37:47
Message-ID: 20070607003747.8641.qmail () ktown ! kde ! org
[Download RAW message or body]
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=136676
kde-bugzilla thequod de changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
everconfirmed|0 |1
------- Additional Comments From kde-bugzilla thequod de 2007-06-07 02:37 -------
1. You need pinentry (e.g. pinentry-qt)
2. You need gpg-agent running
I see two bugs here:
1. The "wrong passphrase" error displayed in the header of the mail is wrong and \
misleading. 2. KMail should not depend on gpg-agent. It should rather fall back to \
the same dialog, that gets used when encrypting a mail: "Passphrase Dialog - KMail"
You need a passphrase to unlock the secret key for user:
KEYID User Name
This dialog will reappear every time the passphrase is needed.
...
For information on how to set up gpg-agent, see
http://kmail.kde.org/kmail-pgpmime-howto.html
2a: There seem to be two different pinentry objects used internally: one for \
encrypting and one for decrypting. I've noticed this, because I had to re-type the \
password when encrypting while I just had typed it for decryption. After it had been \
entered for "both use cases", it was not required again.
If you have further problems, please report what gets displayed on the konsole, when \
you start kmail from there and then access an encrypted mail. This might be \
"gpgme_op_decrypt_verify() returned this error code: 117440523" - that's what I was \
getting when I removed pinentry/gpg-agent.
I suggest using e.g. "keychain", see http://www.gentoo.org/proj/en/keychain/.
Please try keeping this bug item about (fixing) the bug - there should be enough \
workarounds posted now already. _______________________________________________
KMail developers mailing list
KMail-devel@kde.org
https://mail.kde.org/mailman/listinfo/kmail-devel
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic