Looks good to me on gpg4win-5.0.2-beta2 @ win11 (although there might unrelated issues, see notes in the end).
Tests of all messages generated by create-test-data.sh:

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

Looks good to me on gpg4win-5.0.2-beta2 @ win11 (tested via config file and registry)

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

This ticket has been superseded by T7971: Kleopatra: Always use gpgme to find the GnuPG binaries. All changes have been reverted.

This is the dialog window which comes up when importing a team key with the group flag:

Right, looks good to me now on gpg4win-5.0.2-beta2 @ win11:

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

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

Possibly, it was the same cause as T8052 (the bug in libgpg-error spawning a process).

I looked at sm/keydb.c:keydb_set_ephemeral function. It says:

How did you configure? If possible, please show us the configure options when you built.
Did it work in older version(s) of libgpg-error?

tested with Gpg4win-5.0.2-beta2

I don't really know what you are testing, but as far as I understood the (overly verbose [sigh]) comments the only thing that was implemented is that temporary files are removed when our mail viewer is closed properly. Removing temporary files/folders left over on a crash or reboot or any other forceful termination of the mail viewer or kleopatra would be covered by the already mentioned T6842: Kleopatra: Clean up temporary files on windows.

In this comment above T6793: Cleanup temporary files / dirs with decrypted content another issue was created for this: T6842: Kleopatra: Clean up temporary files on windows
I'm not sure what to expect, before this is implemented, so I just documented it here.

I found out, that successful notepad pgp encryption/signature never had an audit log button (it's also like this in gpg4win-4.4.1 and vsd-3.3.4).
So, everything fine here for gpg4win-5.0.2-beta2 @ win11, vsd still needs to be tested.

Suggestion: When Kleopatra starts up, it should just delete its Temp folder.

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

In T7784#214660, @timegrid wrote:

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

In T7784#214657, @timegrid wrote:

Issues found:

• pgp encrypt/sign does not offer an audit log, the first screenshot in the description ("verschlüsselt und signiert") suggests that this was different before

it was zsh

Not sure, which shell had problems, but it works on both zsh and bash with my last build gpg4win-5.0.1-beta24-x86_64.AppImage. So i guess, i can close this.

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

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

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 is used to validate the commits.

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 use of GNU LD.