The testcase now works, gpg4win-beta-50.

I assume we do not want to unify this (yet)? But if we want to, we should make another ticket for this anyway.

I expect that the user can change the expiry date to 01.10.2024 but nothing else.

In T6882#191854, @werner wrote:

While testing this I noticed that only the last adsk or trusted key is listed. Thus several assurances of this options are not properly represented. See T7313

Fixed for master. Let's first test this with kleopatra.

Done for 2.2. It is already in 2.4.

Yes, for historical reasons (i.e. we haven't changed this) the width of the name and email columns always defaults to 260.

tested with gpg4win-Beta50:

FWIW, a related task is T7308

works, gpg4win-Beta-50

Will do.

Alright, we should do that in any case because two key caches are never a good idea and in particualr not if one of them needs too be reloaded too often. Thus re-using the one in Kleopatra is the proper solution. I recall that we looked at this at a time when we already started to design gpgol2 which would solve the problem anyway. However, at least for vsd we need to keep on using the classic gpgol for quite some more time. Thus the effort to improve the key resolving in gpgol is really justified.

done: https://invent.kde.org/pim/kleopatra/-/merge_requests/285

with gpg4win-Beta-50: "Rückstellcode" is shown correctly with an ü

The change will also be included in VSD 3.3.

The version check can now be extended to 2.2.45 <= gpg < 2.3.0.

werner: Can you also backport listing of "default-new-key-adsk" with gpgconf so that Kleopatra can check whether a default ADSK is set?

Fixed. Ready for testing.

Backported for VSD 3.3.

The fix needs to be backported for VSD 3.3.

Note: The code for this is in the work/mmontkowski branch but has not yet been merged with master. Before we take this bug up again, we need to look closer at the ribbon UI events as remarked by Andre on July 29.

This is implemented; just missing the backport that is requested in T7302

Backported to 2.2

gpg4win-beta-50: There are no duplicate announcements of the entries in the result table of a keysearch with NVDA

ok, with gpg4win-Beta-50, a search result is only selected and highlighted if it is the only result.

For the "unknown recipients" there was the good suggestion to not show that line at all. As it has no additional information which is not included in the new explanation. I like that, but only in the case that there are no known recipients at all, as it would be confusing to list only e.g. one known recipients and then not mention the 5 unkown ones, IMHO.

Migration works for upgrade to gpg4win.beta-50, too:
A copy of kleopatrarc is written to the nwely created folder %APPDATA%/gnupg/kleopatra

I guess this is now fixed for all branches.

Ingo suggested additional changes and due to the helpful screenshot in the MR I've got some, too.

works, gpg4win-beta-50

icon is there, gpg4win-Beta-50

works, gpg4win-Beta-50. "Write" occurs at the right point now.

search for "example" works now, Gpg4win-Beta-50

Okay, okay: s/private key/secret key/

The test with Gpg4win 4.3.1 (using GnuPG 2.4) seems to indicate that:

1. gpg didn't update the trustdb automatically after importing the extended trusted certificate.
2. gpg updated the trustdb automatically after deleting and re-importing the expired trusted certificate, but Kleopatra still showed the certificates signed by the trusted certificate as "certified". This could be a bug in the trustdb calculation (note the log message "Schlüssel C5D6C919005F36A4 ist als ultimativ vertrauenswürdig gekennzeichnet" which could indicate that gpg treats the key as valid although it's expired). On the other hand, my test with GnuPG 2.4 on Linux doesn't reproduce this problem.

And I can replicate it with the Appimage for VSD 3.2.2, too.

The issue is the same on import on the command line. So it's a gpg issue.

This was implemented by Tobias

Backported the changes in Kleopatra for VSD 3.3.

Since VSD 3.3 will likely include this change in gpgme I add the vsd33 tag.

Backported for VSD 3.3

Works fine.
For special DOS names only COM/LPT1-9 are supported names like COM12 are not handled.
But that is not really an issue as these names are always prepended with the temp-pathname and c:\tmp\COM12 are valid names.