[Bug 595055] Re: kgpg generates signing only key

[Jonathan Thomas]

** Description changed:

- Binary package hint: kgpg
+ ##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
+ 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-0ubuntu1~lucid1~ppa1
  
  The createk key looks like this:
  
  gpg  --edit-key    9C2526CCDE53F875
- pub  2048D/DE53F875  created: 2010-06-16  expires: 2012-06-15  usage: SCA 
-                      trust: ultimate      validity: ultimate
+ pub  2048D/DE53F875  created: 2010-06-16  expires: 2012-06-15  usage: SCA
+                      trust: ultimate      validity: ultimate
  [ultimate] (1). XXX XXX <XXX at XXX.XXX>
  
  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://help.ubuntu.com/community/GnuPrivacyGuardHowto
  and then key seems to have the sub-key as needed:
  
- pub  2048R/F108C3FB  created: 2010-06-16  expires: 2012-06-15  usage: SC  
-                      trust: unknown       validity: unknown
- sub  2048R/7A152921  created: 2010-06-16  expires: 2012-06-15  usage: E   
+ pub  2048R/F108C3FB  created: 2010-06-16  expires: 2012-06-15  usage: SC
+                      trust: unknown       validity: unknown
+ sub  2048R/7A152921  created: 2010-06-16  expires: 2012-06-15  usage: E
  [ unknown] (1). XXXX <XXX at XXX>

** Description changed:

  ##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
- Testcase: 
+ Patch: http://websvn.kde.org/branches/KDE/4.4/kdeutils/kgpg/transactions/kgpggeneratekey.cpp?r1=1155016&r2=1155015&pathrev=1155016
+ 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-0ubuntu1~lucid1~ppa1
  
  The createk key looks like this:
  
  gpg  --edit-key    9C2526CCDE53F875
  pub  2048D/DE53F875  created: 2010-06-16  expires: 2012-06-15  usage: SCA
                       trust: ultimate      validity: ultimate
  [ultimate] (1). XXX XXX <XXX at XXX.XXX>
  
  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://help.ubuntu.com/community/GnuPrivacyGuardHowto
  and then key seems to have the sub-key as needed:
  
  pub  2048R/F108C3FB  created: 2010-06-16  expires: 2012-06-15  usage: SC
                       trust: unknown       validity: unknown
  sub  2048R/7A152921  created: 2010-06-16  expires: 2012-06-15  usage: E
  [ unknown] (1). XXXX <XXX at XXX>

-- 
kgpg generates signing only key
https://bugs.launchpad.net/bugs/595055
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to kdeutils in ubuntu.