Bug 359954 - cannot update old keys with new subkeys
Summary: cannot update old keys with new subkeys
Status: REPORTED
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: git master
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Andre Heinecke
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-01 15:38 UTC by Sean Engelhardt
Modified: 2021-03-10 00:15 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Sean Engelhardt 2016-03-01 15:38:17 UTC 
given was the following scenario:

We have a certificate, created with gpg2, containing (a) private key(s).
we export this certificate using:
  gpg2 -a --output gpg-secret-key.asc --export-secret-keys <ID>

we edit the certificate using gpg2 --edit-key and addkey to add a new subkey
we export this certificate again using:
  gpg2 -a --output gpg-secret-key-with-sub.asc --export-secret-keys <ID>

In Kleopatra, we import the gpg-secret-key.asc first, which works as expected.
Now we import the gpg-secret-key-with-sub.asc - Kleopatra displays the following message:

"total number processed: 1
 Imported: 0"

Expected:
The certificate were updated with the new key
Kleo shows a new subkey in "Certificate Details" -> "Technical Details"

Result:
The certificate have not been updated
Kleo does not show the new key in "Certificate Details" -> "Technical Details"
Comment 1 Justin Zobel 2021-03-10 00:15:30 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.