Page MenuHome GnuPG

Kleopatra: Change colums in subkey details
Open, NormalPublic

Description

Regarding the subkey details information shown in Kleopatra Werner's suggestions for changes are:

  • replace ID column by Fingerprint column
  • remove Type column
  • the dates (valid from/valid until) should always be given in ISO format
  • change Strength column title to Algorithm and in the contents add the algorithm in the cases where it is missing at the moment (e.g. 2048 -> RSA 2048)
  • remove column Primary, as the primary is always the first one

Additionally I would find it sensible to display the keys always in the order of the keyslots.

I find it irritating when the authentication key is shown in position 2 instead of 3.
But I do not know how the order is determined now and if there is a good reason for this.

Revisions and Commits

Event Timeline

Additionally I would find it sensible to display the keys always in the order of the keyslots.

Which keyslots? I'm pretty sure that Kleopatra shows the subkeys in the order they are listed by gpg -k --with-colons (which is either by creation date or by the order of the subkey packages). If you think that's not true for some key then provide this key.

You are (of course) right, gpg -k shows the keys in that order. Which is different from the order shown in the smartcard management view and what gpg-card shows. So lets drop that point for now and maybe discuss this some time in the future.

aheinecke triaged this task as Normal priority.Jan 26 2024, 4:04 PM
aheinecke added a subscriber: aheinecke.

Regarding https://invent.kde.org/pim/kleopatra/-/merge_requests/106 I cannot login to gitlab right now. Since I have to manually migrate my fdroid apps to the new phone and my 2fa app is one of them. But I agree with everything ingo said there.

Do not start changing the date formatting. We do what Qt does. If the user wants to have ISO formatting he can configure that. Changing that here and not throughout Kleopatra would be just wrong.