Page MenuHome GnuPG

Kleopatra: reorder columns for tables in the new tabs in the certificate details
Testing, NormalPublic

Description

Edited on 2024-08-13 to represent the final order/name changes we want

In some of the new tabs the column order is suboptimal.

We want to start from the order in the certificate list and adapt it to the needs of the new tables:
Name, E-Mail, Status, Valid From, Valid Until, [Protocol], Key ID, [Fingerprint], [Certification Trust], [Origin], [Last Update], [Issuer], [Serial Number], [Tags], [Algorithm], [Keygrip]

Suggestions for tabs, [] means hidden by default:

  • User-IDs
    • now: EMail, Name, Trust Level, [Tags], [Origin])
    • new: Name, Email, Trust Level, [Origin], [Tags]
    • Note: in the main certificate it is still E-Mail (I believe), that would be for another ticket.
  • Subkeys
    • now: [Key ID], Fingerprint, Valid From, Valid Until, Status, Algorithm, Usage, Storage, [Keygrip]
    • new: [Key ID], Fingerprint, Status, Valid From, Valid Until, Usage, Algorithm, Storage, [Keygrip]
    • Note: Status here is not the same as Status in the main certificate list, here it is: good, expired, revoked, [...]. No "certified" and "not certified"
  • Certifications
    • now: User ID / Certification Key ID, Name, E-Mail, Valid From, Valid Until, Status, Exportable, Tags, Trust Signature For)
    • new: User ID / Certification Key ID, Name, Email, Status, Exportable, Valid From, Valid Until, [Tags], Trust Signature For
    • Note: Status here is not the same as Status in the main certificate list, here it is: valid, revoked, [...]
  • Smartcard
    • We decided to remove this tab again, as all relevant info from that is in the subkeys tab already

For reference: Smart card view table as implemented recently by Ingo for PIV: Card Key (aka Slot), User ID, Fingerprint, Created, Usage, Algorithm, Keygrip, Actions

Revisions and Commits

Event Timeline

ebo renamed this task from Draft: Kleopatra: reorder columns for new tab views in the certificate details to Draft: Kleopatra: reorder columns for tables in the new tabs in the certificate details.Aug 2 2024, 11:47 AM

Sorry, I can't resist to quote Knuth from his homepage:

A note on email versus e-mail

Newly coined nonce words of English are often spelled with a hyphen, but the hyphen disappears when the words become widely used. For example, people used to write “non-zero” and “soft-ware” instead of “nonzero” and “software”; the same trend has occurred for hundreds of other words. Thus it's high time for everybody to stop using the archaic spelling “e-mail”. Think of how many keystrokes you will save in your lifetime if you stop now! The form “email” has been well established in England for several years, so I am amazed to see Americans being overly conservative in this regard. (Of course, “email” has been a familiar word in France, Germany, and the Netherlands much longer than in England --- but for an entirely different reason.)

Thus pretty please use email.

Please name the smartcard tab column Slot and use Smartcard instead of Token. Most users either have a “Smartcard” or a “Yubikey” and they don't known what we mean by “Token”.

Actually, it seems to be spelled "smart card" in English (e.g. in Merriam Webster and Oxford English Dictionary). Two words. It's just us ignorant Germans who like to glue words together as if there's no tomorrow.

Please see the quote from Knuth which explains this.

aheinecke triaged this task as Normal priority.EditedAug 5 2024, 3:55 PM
aheinecke added a subscriber: aheinecke.

Name, E-Mail, Status, Valid From, Valid Until, [Protocol], Key ID, [Fingerprint], [Certification Trust], [Origin], [Last Update], [Issuer], [Serial Number], [Tags], [Algorithm], [Keygrip]

^ I would hide key id and show fingerprint by default. In other places we write you should always check the fingerprint. And KeyID is then another confusion word. Is the keyID the fingerprint? What is the KeyID? In the past I was actually for removing this altogether since it adds confusion for the only benifit of showing less information.

Subkeys:

new: [Key ID], Fingerprint, Status, Valid From, Valid Until, Usage, Algorithm, Storage, [Keygrip]

I would move the Fingerprint to the back as before. And also the same with smartcards. There I find "Holder" if that is what is meant by owner to be the most important field as I use that to identify my smartcards.

Note: Regarding the Tags, didn't we say that if tags do exist the column is shown automatically?

"Holder" doesn't exist for anything but OpenPGP cards and many people may not set it. Hence, I think it makes little sense to show this in a prominent location if it's empty for most users who don't juggle with loads of OpenPGP cards.

"Holder" doesn't exist for anything but OpenPGP cards and many people may not set it. Hence, I think it makes little sense to show this in a prominent location if it's empty for most users who don't juggle with loads of OpenPGP cards.

I was trying to think of "why would I want to look at that?" What information could I gleam that would help me decrypt / verify or encrypt / sign something. And I thought well, if I know enough of the smartcard to have the stubs with the Owner / Holder (I assume that means the same thing) then that could be useful. To see which of the subkeys lie on which smartcard. Since here the connection is from one certificate to potentially multiple smartcards. E.g. Related to persons: Who has the projects supersmartcard at the moment. Or e.g. This key is on card "Codesigning 3" or so.

But since this is also covered by Token and since Token is more generic. I can agree with you not to show it prominently, I like it for OpenPGP because I can freely define it.

ebo renamed this task from Draft: Kleopatra: reorder columns for tables in the new tabs in the certificate details to Kleopatra: reorder columns for tables in the new tabs in the certificate details.Aug 13 2024, 2:06 PM
ebo updated the task description. (Show Details)
TobiasFella changed the task status from Open to Testing.Aug 15 2024, 11:28 AM
TobiasFella claimed this task.

Backported for VSD 3.3

ebo moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Tue, Oct 1, 3:55 PM