Bug 390949 - GUI: Add comments and categories to signature adressbook
Summary: GUI: Add comments and categories to signature adressbook
Status: RESOLVED UPSTREAM
Alias: None
Product: kleopatra
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: unspecified All
: NOR normal
Target Milestone: ---
Assignee: Andre Heinecke
URL: https://dev.gnupg.org/T3968
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-23 13:47 UTC by MBB
Modified: 2018-05-08 17:36 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
GUI mockup (139.63 KB, image/jpeg)
2018-02-23 13:47 UTC, MBB
Details

Note You need to log in before you can comment on or make changes to this bug.
Description MBB 2018-02-23 13:47:50 UTC
Created attachment 110935 [details]
GUI mockup

After importing a signature, there seems to be no way to re-name it, you are stuck with the name the creator gave it. When that name is not obvious, it is difficult to later find back who a key beklongs to and why you imported it. (and if it can be removed)

For instance a lot of software is not signed with the name of the program, but by a company or individual developer. When verification fails it would be easier to see if you already have the certificate if you have labeled them.

When youhave many signatures, it may also be usefull to tag and filter certificates with categories, so that you can separate your software sign certificates from your work messages and your friends. (or for different pseudonyms when you need to sign for different work projects)

I have taken the liberty to create a mockup

I'm using Kleopatra on windows myself, but I assume it applies to all platforms equally.
Comment 1 Andre Heinecke 2018-05-08 17:36:35 UTC
Hi,

Uhm. Apologies for overlooking this issue. Bugs.kde.org has a high frequency of issues and sometimes stuff gets lost.

I confirm your request as a valid feature request. To make a development ticket out of this I've opened https://dev.gnupg.org/T3968 which is our preferred issue tracker for Gpg4win (recent Kleopatra versions also link to that.)

I'm resolving this as Upstream, not because it is fixed but because an upstream ticket exists for this, now.

I'll also respond in the Forum :-)