https://bugs.kde.org/show_bug.cgi?id=371004
Bug ID: 371004
Summary: gpg groups using an non-standard id, are not displayed
correctly and can not be edited in kgpg
Product: kgpg
Version: unspecified
Platform: Archlinux Packages
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@opensource.sf-tec.de
Reporter: kdeb...@dergleichrichter.de
Version info:
KGpg
Version 2.18.0
Using KDE Development Platform 4.14.24
Reproducible: Always
Steps to Reproduce:
1. create a group in the gpg.conf with an identifier that is different from the
kgpg default (i.e. use a 0x in front of the fingerprint)
2. check that the group is working in gpg (gnupg supports lots of different
formats for groups)
3. open kgpg/refresh the keylist
4. look for the group you created and if it is there try to edit it with kgpg
Actual Results:
If the group was at one point in the past usable by kgpg (for instance because
it was initially created by kgpg) and later edited outside of kgpg, then
reloading the list will make the group unusable but it will still be visible.
If kgpg was launched after the group started using non-standard ids it will not
even be visible in the key list.
Expected Results:
Groups should be visible and editable irregardless of the used id format. GnuPG
support lots of ID formats in group definitions i.e.: the email address in
UID, full fingerprint of key, long id, short id, long id with leading 0x, short
id with leading 0x, …
It seems that currently kgpg can only handle the full fingerprint without
leading 0x in group definitions. It should support all ID formats in groups
that GnuPG supports, for viewing and editing.
I use groups extensively for mailing lists and company internal communication.
I guess these functions are not used a lot by most users. My workaround for
groups is to use a text editor on the gpg.conf and copy paste everything around
from gpg in konsole.
--
You are receiving this mail because:
You are watching all bug changes.
