kmail always tries all keys, and asks for passphrases without need, if you have several private keys that match OpenPGP message
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kdepim (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: kdepim
If I have an message that is encrypted for OpenPGP keys A B and C,
and I do have private keys of A and B,
then kmail will always ask me for passhprase to key A, even if key B is already "opened" (cached passpharse).
1. have email encrypted for OpenPGP keys A B and C
2. have private key of A and B
3. open that email in kmail
4. you are asked for passprhrase for A
5. cancel it
6. you are asked for passprhrase for B
7. enter it
8. message is decrypted
so far all is ok, but the problem is:
9. select again this email or other similar email
10. you are asked for passphrase to A
11. cancel it
12. message is decrypted (using key B)
Insted, expected result would be to skip step 10 and 11
ProblemType: Bug
Architecture: amd64
Date: Sun Jan 10 14:36:08 2010
DistroRelease: Ubuntu 9.10
NonfreeKernelMo
Package: kmail 4:4.3.2-0ubuntu6
ProcEnviron:
LANGUAGE=
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: kdepim
Uname: Linux 2.6.31-17-generic x86_64
summary: |
- kmail always asks for all passphrases if you have several private keys - that match OpenPGP message + kmail always ties all keys, and asks for passphrases without need, if + you have several private keys that match OpenPGP message |
summary: |
- kmail always ties all keys, and asks for passphrases without need, if + kmail always tries all keys, and asks for passphrases without need, if you have several private keys that match OpenPGP message |
Hi there,
Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https:/ /bugs.kde. org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.
Thanks!