Bug 359954

Summary:	cannot update old keys with new subkeys
Product:	[Applications] kleopatra	Reporter:	Sean Engelhardt <omniasoltemperat>
Component:	general	Assignee:	Andre Heinecke <aheinecke>
Status:	REPORTED ---
Severity:	normal	CC:	mutz, pim-bugs-null
Priority:	NOR
Version First Reported In:	git master
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

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.