A different order is pretty much impossible to implement in upstream kconfig without big changes/refactoring.

Also done: The tab order for the close button is now correct.

Note: On gpg4win-5.0.1, there's also no audit log for notepad pgp sign/encrypt. So this is expected?

Looks good to me on gpg4win-5.0.2-beta2 @ win11.

Just to be sure: The "Show Email" button is still never shown on the notepad, right?

In general looks good to me on gpg4win-5.0.2-beta2 @ win11:

Looks good to me on gpg4win-5.0.2-beta2 @ win11:

• first manual gpg -K and gpgsm -K displays the correct output now
• the loop ran without a hang for 50 times

Looks good to me on gpg4win-5.0.2-beta2 @ win11:

Looks good to me on parallel install of

1. gpg4win-5.0.2-beta2 @ win11
2. vsd-4.0.0-beta1203 @ win11

Looks good to me on gpg4win-5.0.2-beta2 @ win11:

The registry keys "GnuPG Desktop" and "GnuPG VS-Desktop" now work correctly, i.e. existing registry keys should be considered in the next VSD 4 build.

There shouldn't be any RegCreateKey anymore for HKLM\SOFTWARE\<product name>\... or HKCU\SOFTWARE\<product name>\.... And, of course, no registry keys should be created.

In any case, the order still needs to be adjusted.
The current implementation in gpg4win-5.0.2-beta2 is still (neither the order in the description nor on the settings page):

Seems to work in principle with gpg4win-5.0.2-beta2 and vsd-4.0.0-beta1203.
I'll wait for a new vsd beta release (with some fixes) for further testing.

with Gpg4win-5.0.2-beta2:

The missing signature indication can also be seen now in the customer mails sent via kmail (ted:INBOX, e.g. 18.02. 12:52). This was fine before.

Looks good to me on gpg4win-5.0.2-beta2 @ win11.
Tested import on 5 normal starts and 5 gdb starts.

The basic fix for the msg box looks good to me on gpg4win-5.0.2-beta2 @ win11.
There's only no signature shown anymore, not even for the formerly working case 1.
Note: I also tested those mails sent to an exchange server with the same result as via IMAP.

Looks like the "read config from registry" patch that was upstreamed wasn't tested properly.

It seemed that the reporter (also) claimed that a git repo could be weak/vulnerable when X.509 signature (with a relevant curve key) is used to validate the commit.

For the record (to show we don't hide a problem), I add some information.

It should be solved by the upstream (libtool, gnulib, and possibly autoconf/automake). The solution would be refactoring AC_PROG_LD and AC_LIB_PROG_LD factoring out common things like handling of use of GNU LD.

Works with Gpg4win-5.0.2-beta2

Fixed.

Here's a full log of a gdb run, which segfaults on start:

full debugview log with a crash on import after trusting the root cert:

Please always attach the full Debugview log. Sometimes (like here) I really want to know everything that was logged since the start.

Fixed. This regression was caused by changes made for T8056: Support config options RSAKeySizes and PGPKeyType for Kf6.

Implemented in mimetreeparser master: https://invent.kde.org/pim/mimetreeparser/-/merge_requests/92