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.

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)

ok, here the comments from our joined feedback session:

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".)

This is how it looked before (VSD 3.2.2):

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):

I did what you did, didn't even need to restart 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.

You could use colors, fonts, icons to mark any certificate you want instead of having to use tags and filter by them. You could even put their company logo on certificates of your communication partners.

As it was a fresh install of a gpg4win test version I used: yes, common.conf was not only supposed to be there, it is and keyboxd.exe is shown in the task manager.
But I think it not only needs to be solved for keyboxd, as our VSD customers don't have that.

From the support angle, the worst of these issues is that the default will not be restored for VS-NfD. But then: nobody has inquired about that yet…

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)

As for renaming "Change Reset Code" to "Set Reset Code", what about "Change PIN" and "Change Admin PIN"? Should they also be renamed? If not, why not? Is there no default reset code? Is there a way to find out whether the reset code has already been set (in which case "change" would be more appropriate than "set")?

ok, I like your proposal. To recap:

I'm not sure if we are talking about the Encrypt-to-self drop-down or the Encrypt for others input fields. On the other hand, I see little reason to treat both differently.

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:

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:

Well, i can live with it. It would be an improvement.
I would prefer if no import tab was created if a key has not been updated and therefore nothing was actually imported. But I see that this would be more complicated to implement and I have no strong opinion on this anyway.

On a fresh install Version 3.2.2.2405000+git~ (Gpg4win-4.3.2-beta35) are now all available columns displayed by default:

Tested with version 3.2.2.2405000+git~ (Gpg4win-4.3.2-beta25)

In Version 3.2.2.2405000+git~ (Gpg4win-4.3.2-beta25) the button is not shown any more.
As it was already not shown in VSD 3.2.2, closing this for all workboards

Then I would propose to add additional text at the top of the tool tip for VSD versions only. Something along the lines of: "Please check with the approval document whether this function is compliant for your smart card model."
Would that be possible?

What makes a card compliant? is it just about supporting algorithms that are compliant?

A minimal fix would be:

In reply to Ingo:
Ok, I can live with that but I still would like this message to be improved.
Looking at it some more I noticed some other details which bother me:

sorry, imprecise phrasing … we want this to be used in practice, which includes making the creation of a combined signature file easier.

After discussion we concluded that showing all signatures in one detached signature file is something we want soon.

After talking with Werner, I edited T7155 to include displaying the protocol column, too, because this is useful in combination with his wishes regarding the origin keyword which are:

Looking only at the text used, you get exactly the same messages used for single certificate updates, "The certificate has been updated" or "The certificate was not found.", both in the singular.

And "But "Update certificate" does still not query WKD (not even after restarting Kleopatra.)" seems to happen because the setting "Query certificate directories of providers for all user IDs" wasn't enabled.