Page MenuHome GnuPG

Improvement proposal for the trusting process (Beglaubigung)
Closed, ResolvedPublic


Referring to the attached screenshot, the form would support the trusting process much better, if the fingerprint...

  • would be presented in a better readable way (e.g. bigger letters, in an own paragraph with more space around to focus the user on this part of the dialog, or similar)
  • if the fingerprint could be selected and copied to the clipboard, in order to use any compare or search function, e.g. a web browser's one when comparing the fingerprint on a website.

The luxury variant would be to provide the compare functionality in this dialog, i.e. provide an edit field where the user can manually enter the fingerprint to be compared (e.g. during a verification phone call) or copy and paste it from a trusted website.


3.1.8-gpg4win-3.1.10 5.55.0, Gpg4win

Event Timeline

aheinecke triaged this task as Normal priority.
aheinecke added a subscriber: aheinecke.

Hi Florian,

we had the same idea. I've just polished this dialog last week. :-)

E.g. Printing the primary user id in the bottom I found fairly useless because that information is already avaliable at the top. And I also removed the annoying "I have checked the fingerprint" check box, and replaced it with an explanation why users should check the fingerprint.

I'll add a screenshot here later so that you can comment.


With the new version we get an even more extensive rework of the certify dialog. We now also have support for search tags.

It will now select all user ids by default. The secret key selection uses the combobox widget from the file encryption and stores the last selected key. Exportable or not is also stored so it is selected automatically based on how you selected it the last time.

To certify my key with all userids you previously needed 11 clicks. Now you need 1. So this is more usable for me, especially when "bulk signing" after a key signing session.

I did not want to move the fingerprint verification process more prominent with an entry field or something like that.

For most users it is in my opinion better to just certify a key once, so we make that easy now. And then they can detect if that key changes. Currently they most likely don't certify and so they don't see if that key changes. It's directing users a bit to some kind of Trust on first use.

Will be greatly improved with 3.1.11