[Bug 451719] Re: kmail cannot sign mails, but can crypt them
Bug Watch Updater
451719 at bugs.launchpad.net
Mon Apr 13 05:58:09 UTC 2015
Launchpad has imported 28 comments from the remote bug at
https://bugs.kde.org/show_bug.cgi?id=179997.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.
------------------------------------------------------------------------
On 2009-01-08T09:24:16+00:00 LtWorf wrote:
Version: KMail: 1.10.92 (using Devel)
OS: Linux
Installed from: Compiled sources
When i try to send a gpg signed mail, a popup says that it can't sign
because of "bad passphrase". Well i bet it should ask me to insert the
passphrase before passing it to gpg, and i am not prompted to insert
it.. So obviously it doesn't work.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/0
------------------------------------------------------------------------
On 2009-01-09T17:03:52+00:00 Luis Silva wrote:
I can confirm this with launchpad/kubuntu ppa packages for kde 4.2 beta
2.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/1
------------------------------------------------------------------------
On 2009-01-16T15:25:24+00:00 Anne Wilson wrote:
That sounds as though you don't have pinentry-qt installed
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/2
------------------------------------------------------------------------
On 2009-01-16T17:29:36+00:00 LtWorf wrote:
I don't have it installed... But I can read encrypted mails. And to do that i need to enter the passphrase.
I'll try what happens if i install it, and if it works i'll report to debian to add it to dependecies.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/3
------------------------------------------------------------------------
On 2009-01-16T20:27:49+00:00 LtWorf wrote:
I've tried installing it... Nothing changes.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/4
------------------------------------------------------------------------
On 2009-01-26T18:29:07+00:00 cassianoleal wrote:
I can confirm the problem with KDE4.2 from http://kde42.debian.net/ . I
have installed pinentry-qt4 but nothing has changed.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/5
------------------------------------------------------------------------
On 2009-05-13T11:35:18+00:00 LtWorf wrote:
Now i can read encrypted messages, but still i can't sign. I guess this
means that the pinentry stuff is correctly installed and you will
finally admit it is a bug... The message i get now when i try to sign is
that the recipient doesn't have encryption preferences. Am i supposed to
set those preferences for each item in my address book? I'll be old when
i finish...
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/6
------------------------------------------------------------------------
On 2009-05-13T13:22:11+00:00 Anne Wilson wrote:
(In reply to comment #6)
> Now i can read encrypted messages, but still i can't sign. I guess this means
> that the pinentry stuff is correctly installed and you will finally admit it is
> a bug... The message i get now when i try to sign is that the recipient doesn't
> have encryption preferences. Am i supposed to set those preferences for each
> item in my address book? I'll be old when i finish...
Calm down :-) I had exactly the same problem as this for some time.
After long investigation it turned out that something on my keyring was
corrupt. It's simple enough to test for this. Back up your keyring,
then remove gpg from your system, and start afresh so that it creates an
empty keyring. Import your own public key, and replace your private
keyring from the backup file. If signing now works there is a
corruption in the old keyring.
As for the message about contacts, I don't know whether it is connected
with the other problem, or whether it is a distro-specific problem.
I've never seen it. Try the new-keyring solution first.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/7
------------------------------------------------------------------------
On 2009-05-13T15:16:29+00:00 LtWorf wrote:
Bad passphrase...
And since my key is RSA with RSA subkey, it complains because it says it is impossible to use it to sign (false).
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/8
------------------------------------------------------------------------
On 2009-05-13T17:11:38+00:00 Anne Wilson wrote:
(In reply to comment #8)
> Bad passphrase...
> And since my key is RSA with RSA subkey, it complains because it says it is
> impossible to use it to sign (false).
Please quote exact error messages.
Have you tried the new keyring solution?
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/9
------------------------------------------------------------------------
On 2009-05-13T17:28:55+00:00 LtWorf wrote:
Bad passphrase was the message i got after doing the keyring thing and
after editing the recipient contact to walkaround the problem i had
before.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/10
------------------------------------------------------------------------
On 2009-05-13T17:49:15+00:00 Anne Wilson wrote:
Please describe exactly what you have done - removed and reinstalled
gpg? started a new, clean key-ring? re-installed pinentry-qt?
Especially, describe the 'contact editing' that you did. Plus anything
else that might have a bearing on this. The more information you can
give, the better your chances of finding the problem and fixing it.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/11
------------------------------------------------------------------------
On 2009-05-13T18:34:42+00:00 LtWorf wrote:
I deleted the ~/.gnupg directory. Then i imported my public key from keyserver and then i copied private keys.
Then i opened kaddressbook, opened myself contact and set openpgp/mime in cryptographic settings.
Then i tried to sent to myself a signed mail, and the old and familiar bad passphrase without the asking dialog first appeared.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/12
------------------------------------------------------------------------
On 2009-05-13T20:41:59+00:00 Anne Wilson wrote:
(In reply to comment #12)
> I deleted the ~/.gnupg directory. Then i imported my public key from keyserver
> and then i copied private keys.
> Then i opened kaddressbook, opened myself contact and set openpgp/mime in
> cryptographic settings.
> Then i tried to sent to myself a signed mail, and the old and familiar bad
> passphrase without the asking dialog first appeared.
Have you set up Configure KMail > Identities > (Highlight identity)
Modify > Cryptography tab? You need to set your key for both signing
and encrypting if you are going to use both.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/13
------------------------------------------------------------------------
On 2009-05-13T22:29:31+00:00 LtWorf wrote:
I did.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/14
------------------------------------------------------------------------
On 2009-05-13T22:38:40+00:00 cassianoleal wrote:
I have created an executable file called ~/.kde/env/gpgagent.sh with the
following contents:
eval "$(gpg-agent --daemon)"
This came from a comment in an Ubuntu bug, but I can't find the link
right now. The dialogue asking for a passphrase has been popping up
since then. Don't forget to make the file executable and logging out of
/ into KDE.
I still find that it's a bug, but this workaround has worked for me.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/15
------------------------------------------------------------------------
On 2009-10-21T02:57:02+00:00 anselmo wrote:
I had this problem in the past, it works here now, using
Qt-4.6.0-beta1
KDE Version 4.3.72 (KDE 4.3.72 (KDE 4.4 >= 20091015))
KMail Version 1.12.90
Can anyone else recheck this? Thanks
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/20
------------------------------------------------------------------------
On 2009-10-21T02:57:24+00:00 anselmo wrote:
*** Bug 211107 has been marked as a duplicate of this bug. ***
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/21
------------------------------------------------------------------------
On 2009-10-27T20:54:47+00:00 Alain Baeckeroot wrote:
How can this bug can be tagged resolved, when the brand new 4.3 suffers
from it, and makes kmail unusable !
On 4th August 2009, KDE 4.3.0 was released by the KDE community and no
distribution is shipping 4.4 !
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/23
------------------------------------------------------------------------
On 2009-10-27T20:56:56+00:00 Alain Baeckeroot wrote:
the workaround given in #15 does not work for me.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/24
------------------------------------------------------------------------
On 2009-10-27T21:50:26+00:00 Anne Wilson wrote:
This is not a KDE issue, as far as I can see. I an many others sign and
encrypt mail in KMail. On the other hand, it could possibly be a
packaging issue, so you should file a bug report with your distro.
I find it strange, though, that getting gpg-agent to work actually
activated the pinentry-qt. That should have worked without gpg-agent.
The agent's task is to cache your passphrase for a set length of time so
that you don't have to enter it for every message you sign. The fact
that it did work (Comment 15) does point to a distro bug.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/25
------------------------------------------------------------------------
On 2009-10-27T23:53:32+00:00 LtWorf wrote:
I did fill a bugreport for debian linking this bug. I guess at this
point we users just have to sit and watch the fight.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/26
------------------------------------------------------------------------
On 2009-10-28T10:48:36+00:00 Cgiboudeaux wrote:
Installing pinentry-qt or pinentry-qt4 is not enough if you don't tell
gnupg to use it.
http://userbase.kde.org/KMail/PGP_MIME#Issues for more informations.
(It's not up to KMail to configure gnupg, sorry)
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/27
------------------------------------------------------------------------
On 2009-10-28T11:10:23+00:00 Anne Wilson wrote:
Of course, and that's the reason I suggested creating the gpg-agent
config file. However, since the reason for that file is unrelated to
pinentry-qt it seems strange that it is the only place I can think of
where the instruction exists. Since I've been using such a setup for
years, using the same config files in fact, I can't honestly remember
how I originally got it to work. I do remember times after a new
install when I was asked for the passphrase for every message, which
suggests that agent is not necessary, though obviously desirable.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/28
------------------------------------------------------------------------
On 2009-10-28T12:40:05+00:00 Alain Baeckeroot wrote:
Finally it works :-) thanks to #22 and the installation of pinetry-qt4
and reconfiguration with kgpg.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/30
------------------------------------------------------------------------
On 2010-05-05T22:18:45+00:00 LtWorf wrote:
Using gpg-agent allowed me to sign, but i still think there is something
wrong.
Without gpg-agent and pinentry i can actually enter my passphrase and
READ the encrypted emails in my inbox, but i can't sign and i can't read
the emails encrypted with my own key in my outbox.
I would expect a more consistent behaviour: either kmail can work
without the agent or can't, but this.. partial working is nonsense IMHO.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/32
------------------------------------------------------------------------
On 2010-08-05T15:42:46+00:00 Envite wrote:
Check if duplicate of 233277
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/33
------------------------------------------------------------------------
On 2015-04-12T10:24:06+00:00 Montel-3 wrote:
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.
Reply at:
https://bugs.launchpad.net/ubuntu/+source/kdepim/+bug/451719/comments/34
** Changed in: kdepim
Status: New => Unknown
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdepim in Ubuntu.
https://bugs.launchpad.net/bugs/451719
Title:
kmail cannot sign mails, but can crypt them
To manage notifications about this bug go to:
https://bugs.launchpad.net/kdepim/+bug/451719/+subscriptions
More information about the kubuntu-bugs
mailing list