Tracking of the GnuPG VS Desktop version 3.3.x
Details
Yesterday
With Version 3.2.2.2405000+git~ (Gpg4win-4.3.2-beta41) I see the expected result. The width for the additional columns is as expected too. So I'll mark this task as done.
Thu, Jul 25
Version 3.2.2.2405000+git~ (Gpg4win-4.3.2-beta41):
works as described with pkcs#15 and netkey cards.
(The column width is then the same for those cards)
Wed, Jul 24
The latest changes have been backported for VSD 3.3.
The order of states is "expired", "revoked", "disabled", "invalid", "certified", "not certified". Since we show only one state we need to define an order. I guess it would make sense to give "disabled" the highest priority. (I also think that "revoked" should have higher priority than "expired".)
Tue, Jul 23
This is how it looked before (VSD 3.2.2):
And you could set the expiry date to a later date than the primary key (at least it was shown that way).
Well, now it does not occur for me any more, either. Ok, I'm setting this to resolved, this was most likely a situation where Kleopatra could not write to the kleopatrastaterc (in %APPDATA%\kleopatra\) for some reason. This would then be a more general issue, anyhow, for which we need another ticket if we can reproduce this.
with Version 3.2.2.2405000+git~ (Gpg4win-4.3.2-beta41):
can't reproduce either
I did what you did, didn't even need to restart Kleopatra.
I cannot reproduce this with Version 3.2.2.2405000+git20240712T143635~6033869e1. I open the Details window, go to Subkeys, right-click table header, select Keygrip, close Details window, open it again, go to Subkeys, Keygrip column is still shown. Even after restarting Kleopatra.
With Version 3.2.2.2405000+git~ (Gpg4win-4.3.2-beta41) II can add a keygrip column to the subkey details. But if I close the details window and open it again, the column are no longer selected.
Thu, Jul 18
Wed, Jul 17
ok, works with Version 3.2.2.2405000+git~ (Gpg4win-4.3.2-beta41).
works now, Version 3.2.2.2405000+git~ (Gpg4win-4.3.2-beta41)
Mon, Jul 15
Tue, Jul 9
fixed in https://invent.kde.org/pim/kleopatra/-/merge_requests/243; we were not calling the visibility logic when initially creating the view.
https://invent.kde.org/pim/kleopatra/-/merge_requests/242
- Don't show the tab if the certificate list was empty before the import
- Show tab when any keys were considered, not only when any keys were imported
Mon, Jul 8
ok, new try. As Ingo now clarified that that "nothing was imported" and "nothing was considered" is synonymous for him, then I misunderstood that comment. As far as I understand the "considered" that would mean that a tab would come up for import of unchanged keys, too.
ok, to make it clear how exactly to implement and test this, let me rephrase what my interpretation of your comment is:
Fri, Jul 5
Just a small addendum to what Andre wrote: Obviously, no tab should be shown if nothing was imported.
The final (known) encoding problem with broken umlauts in German error descriptions should be fixed.
The ticket mentioned in the previous comment is T7190: Kleopatra: wrong claim of update in WKD for keys with no mail address.
If one or more keys are refreshed and none of the keys has non-revoked user IDs with email addresses then Kleopatra shouldn't report a result for WKD anymore.
Backported for VSD 3.3.
Turns out
- the singular instead of plural in the German version is a translation thing and should now be fixed (but is not in the testversion beta35)
- there is another issue muddying the waters regarding search in WKD, for which I will create another ticket
I have to correct myself. After restarting Kleopatra, only the following columns are shown, without any changes from my side: