[kleopatra] [Bug 359954] New: cannot update old keys with new subkeys

[Sean Engelhardt via KDE Bugzilla]

https://bugs.kde.org/show_bug.cgi?id=359954

            Bug ID: 359954
           Summary: cannot update old keys with new subkeys
           Product: kleopatra
           Version: git master
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: aheinecke at intevation.de
          Reporter: omniasoltemperat at yahoo.de
                CC: kdepim-bugs at kde.org, mutz at kde.org

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"

-- 
You are receiving this mail because:
You are on the CC list for the bug.