Page MenuHome GnuPG

Kleopatra: Simplify Ownertrust dialog
Closed, ResolvedPublic

Description

From user feedback and personal Experience I find the Ownertrust dialog in Kleopatra too complicated for our target audience. If someone wants to set marginal owner trust the command line should be used.

I would like to have this dialog simplified to:

Do you want to allow <Primary UserID KeyID> to mark certificates as valid (VS-NfD compliant) for you? (VS-NfD of course only in the VS-NfD Mode)

Below in Italics: "This means that you trust the owner of this key to check fingerprints and confirm the identities of others by accepting their certifications as trustworthy."

[Yes] [No]

No-> Unknown trust
Yes-> Full trust

If the Secret Key is aviailable instead:
Is <Primary UserID KeyID> your own certificate?
[Yes] [No]

Yes -> Ultimate Trust
No -> Open the Dialog for a third party certificate next (the one above).

Wording is mostly a suggestion but I think this would be enough.

Event Timeline

aheinecke triaged this task as Normal priority.Aug 23 2022, 3:39 PM
aheinecke created this task.

I am fine with that. No need for the WoT bells and whistles

For better usability and accessibility the [Yes] [No] buttons should be something like [Trust Owner] [Don't Trust Owner] resp. [Yes, This is My Key] [No, That's Not My Key].

Sure. I think we can do this after 3.1.24. I don't want to have additional string changes now as we have translation at 100%

ikloecker moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.
ikloecker changed the task status from Open to Testing.Nov 14 2022, 9:17 AM
ikloecker removed ikloecker as the assignee of this task.
ikloecker moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.

Ready for testing

The simplification works as described except in the following case for importing a private key:

No -> Open the Dialog for a third party certificate next (the one above).

Here the "Mark Own Certificate" opens a second time if you choose no.

I think here "No" should do the same as "Abort" and no second window should come up.
Certifiying a secret key which is not my own does not make sense to me. And should somebody need it anyway, they can always do it in a second step.

ebo claimed this task.

See T6474 for the remaining issue.

ebo moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Apr 26 2023, 12:26 PM