Page MenuHome GnuPG

Kleopatra: Do only ask for confirmation twice when deleting a secret key
Testing, NormalPublic

Description

Currently, when you delete a secret key from Kleopatra you get asked for confirmation twice by Kleopatra and then gpg asks via pinentry window for confirmation for every subkey.

So you have to confirm 4 (!) times for the deletion of the key.
And if you do not always answer "delete" you may end up with a key with out primary. Which is probably not what the user intended.

Please remove the pinentry dialogs and delete the whole key after the second confirmation.

Details

Version
VSD 3.3.0, Gpg4win 4.4.0

Event Timeline

ebo renamed this task from Kleopatra: Do only ask for confirmation once when deleting a secret key to Kleopatra: Do only ask for confirmation twice when deleting a secret key.Feb 20 2025, 3:48 PM
werner triaged this task as Normal priority.Feb 21 2025, 9:11 AM
TobiasFella mentioned this in Unknown Object (Maniphest Task).Nov 17 2025, 9:49 AM
TobiasFella changed the task status from Open to Testing.Nov 21 2025, 2:34 PM
TobiasFella moved this task from Backlog to WIP on the gpd5x board.
ebo moved this task from QA to Done on the gpd5x board.

Gpg4win-5.0.0-beta476:

Ok, only 2 confirmations after the one above any more (for a standard key), they look like this:


It is one for every subkey. If you say "Yes" the first time and "No" the second, you end up with a certificate missing the primary key.
This should ideally be made easier to understand for users.

For one thing, the presentation of the dialog could be improved, with a newline after the question, the certificate name in bold instead of parenthesis and without the trailing "?" in a line on it's own. And probably some more explanation. But this will go in a new ticket.

Note to self: the dialog question is different if the main key was already deleted beforehand. Then there is only the very first question with the warning text, you do not get the pinentry-window question for the single key.

Forget my comment above. Or consider it as the "before" part of the task description…

The changes need gpgmepp and gpgmeqt versions > 2.0.0

ebo moved this task from Done to WIP on the gpd5x board.
timegrid added a subscriber: timegrid.

Curent state in gpg4win-5.0.2-beta-2 @ win11

  • it asks for each subkey
  • but no pinentry involved

Is this fine now?

Note: It could be helpful to add the key usage in the confirmation dialog.


Deletion of a key with primary key with 4 subkeys => 5 confirmations

PS C:\Users\g10> gpg -K multiple-subkeys
sec   ed25519 2026-03-04 [SC] [expires: 2029-03-04]
      5BC9F9B7CD73D0970C1F91BFBC783AB03657A912
uid           [ultimate] Multiple Subkeys <multiple-subkeys@gnupg.test>
ssb   cv25519 2026-03-04 [E] [expires: 2029-03-04]
      7D10DC39F056AEBD1D1C764D9E87C0B552DEB474
ssb   cv25519 2026-03-04 [E] [expires: 2029-03-03]
      098DEBA6C0833E0E803C6A684A13D024C5AE653E
ssb   ed25519 2026-03-04 [S] [expires: 2029-03-03]
      2C71733B86A5FEF133FE7A42534471900A023C42
ssb   ed25519 2026-03-04 [A] [expires: 2029-03-03]
      C39228CA2C88EB3294A2436F574CBBD8772B16D8







well, you are showing 4 pinentry-qt windows above. The reference to pinentry meant those windows.

But no, this is not solved, as the aim was to get rid of the pinentry windows.

ikloecker removed a project: needs discussion.
ikloecker added a subscriber: ikloecker.

There's something wrong. I suspect that gpgme is too old. Yeah, gpg4win 5 uses gpgme 2.0.1 and gpgmepp/gpgmeqt 2.0.0. The changes to force deletion was added later.

I'm moving this back to WIP until gpgme has been updated in the gpg4win builds.