kgpg generates signing only key
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KDE Utilities |
Fix Released
|
Medium
|
|||
kdeutils (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
Lucid |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
##SRU Info added by Jonathan Thomas##
Impact: When a user creates a DSA key, the corresponding ElGamal signing key is not created, leaving the user unable to encrypt files
Addressed by: KGpg has released a patch that fixes the arguments passed to GnuPG for key generation
Patch: http://
Testcase:
1) Run KGpg
2) Ctrl+N
3) Follow key pair creation process. (DSA+ElGamal)
4) Dolphin
5) Select a file to encrypt
6) Choose a key you have created, you will not be able to sign it.
Regression potential: Very small, as it is just correcting the command line arguments passed to GnuPG
#######
kgpg - generate keypair, creates a key that works only for signing, not for encryption.
ii kgpg 4:4.4.4-
The createk key looks like this:
gpg --edit-key 9C2526CCDE53F875
pub 2048D/DE53F875 created: 2010-06-16 expires: 2012-06-15 usage: SCA
[ultimate] (1). XXX XXX <email address hidden>
and it is not possible to use it to encrypt to it, the key seems to miss a sub-key.
So instead user needs to for example generate the key from CLI, like on https:/
and then key seems to have the sub-key as needed:
pub 2048R/F108C3FB created: 2010-06-16 expires: 2012-06-15 usage: SC
sub 2048R/7A152921 created: 2010-06-16 expires: 2012-06-15 usage: E
[ unknown] (1). XXXX <XXX@XXX>
Changed in kdeutils: | |
status: | Unknown → Fix Released |
description: | updated |
description: | updated |
Changed in kdeutils: | |
importance: | Unknown → Medium |
Actually, the above keys where generate on [Lucid], on kgpg 4:4.4.2-0ubuntu1
and identical problem occures on version from Lucid-proposed kgpg 4:4.4.4- 0ubuntu1~ lucid1~ ppa1