To clarify. And what I think might still not work here. Windows has the problem that it does not remove the temp directory on restart or even attempts to. So whenever we work with temporary files we need to make an effort to remove them. Because the user does not expect a decrypted file in a temporary folder to stick around forever. There are options to do that on Windows. As a last resort one could even create a registry key like we did in the uninstaller for a while to remove files which were in used after next reboot.

looks good to me on gpg4win-4.4.1-beta59@win10

looks good to me on gpg4win-4.4.1-beta59@win10

looks good to me on gpg4win-4.4.1-beta59@win10

looks good to me on gpg4win-4.4.1-beta59@win10

No error message in that case for Gpg4win 4.4.o either

This is about attachments of encrypted emails opened with the mail viewer that Carl wrote. If one opens those attachments with an external application then the decrypted attachments are written to temporary files. I don't see that this has anything to do with Kleopatra (unless the mail viewer is considered part of Kleopatra which, technically, it isn't).

QA would like to now what exactly to test here… if there is a succinct description of that in a ticket, it will get tested at the very least sooner. Or at all.

works with Gpg4win 4.4.0, too

Should definitely work with gpg4win if it works with vsd.

That was resolved with vsd 3.2.0

To clarify: this works for "Restart background processes" only, as was the aim of this ticket

forgot to keep it open for test with gpg 2.4 branch versions...

In T6813#184976, @ebo wrote:

Works on Gpg4win 4.3.1, too.

But noticed an inconsistency for the key creation via GpgOL: Contrary to the behavior for key creation in Kleopatra in Gpg4win, you are asked for a password for the new key.

Works on Gpg4win 4.3.1, too.

No more additional dirmngr.exe processes come up in VS-Desktop-3.1.92.39-Beta, too.

Note to self: The error message that nothing was found on the keyserver will still come up if one is configured. That will be fixed with T6493.

The certificates from the same test smart card work in Version 3.2.2.231170 (Gpg4win-4.3.1), too, but there all certificates are shown, that is one more than in the VSD version. Seems gpg2.4 can handle certificates which 2.2 does not accept. But that is nothing to complain about.

Arghh, a GPGME_DEBUG=3 which shows basic I/O preparation does not exhibit the bug.

Fixing gpg is easy but there is some bug lingering in gpgme which might be a recent regression. An strace shows