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

Hidden for Gpg4win-4.3.0-beta571, too

works in Gpg4win-4.3.0-beta571

Fixed in gpgme and gnupg 2.2/2.4.

I applied a fix to gnupg which also solves the issue.

Taking over

We did this on purpose once - For Windows ppl it is just weird to see forward slashes.

In T6833#181135, @werner wrote:

The fix should go into gpgme to spawn dirmngr with a proper home directory (i.e with forward slashes).

I think the double backslash quoting happens because _gpgme_io_spawn quotes the backslashes and calls gpgme-w32spawn and then gpgme-w32spawn quotes the backslashes again and calls gpgconf. I haven't seen anything in gpgme-w32spawn that would unquote the quotes backslashes. But maybe that's supposed to happen in the background. A comment in the code reads "We have to quote some things because under Windows the program parses the commandline and does some unquoting.", but maybe that's no longer true.

Double backslash quoting is the culprit. For WKD requests the GPGMe QT code makes sure that the dirmngr has been started. This is done by running gpgconf --homedir FOO --launch dirmngr. gpgconf returns the homedir with backslashes on Windows to be be nice to ppl who wonder when they notice (legal) forward slashes on Windowns. Now when the spawn function along with its helper is called, it needs to quote the backslashes. But somewhere on the way back one de-quoting is missing and thus gpg sees double backslashes. That is in general not a problem but when checking whether this is the standard home directory, this does not match and gpg puts the socket into a subdirectory. In turn another dirmngr is started for the WKD purpose.

It is still there in VS-Desktop-3.2.1.0 insofar as 2 dirmngrs are started. It was only fixed insofar that it is no longer more than 2.

Since this is hard / impossible to test for, but the fix was obvious I am closing this directly. The fix for this is in GpgOL 2.5.12.

For the record. The code used to detect early on if the dark or bright icon theme should be loaded as a resource caused a crash during startup on at least Windows Server 2016 Enterprise. Our new fix avoids such API but I have created T6921: Kleopatra / Qt6: Improve accessibility detection for "Desert" high contrast scheme and fix it upstream to keep track of this since our fix is not fully complete in that it does not properly detect the Bright (Desert) High contrast mode and it should either be merged into KIconThemes or fixed in / with Qt6.

moved to milestone 3.2.0, as 3.2.1 does not exist as column...

Note for myself: This is the behavior for key resolving in GpgOL. GpgEX has different code for this and the above examples will not work.
In GpgEX the group is not resolved into its component keys currently.

This does not need to be checked again for Gpg4win since the installation of this file is generated from the Gpg4win installation script.

and with a renamed file:

Werner said it is ok

works with VS-Desktop-3.1.90.302-Beta:

works with VS-Desktop-3.1.90.302-Beta, very nice!

The Keyresolver did not allow me to encrypt to an S/MIME cert where the root CA was not in my trustlist.txt that was part of this feature to allow users to encrypt "non vs-nfd compliant" to such untrusted keys, like they would be able to also encrypt to untrusted openpgp keys.

Similarly if you decrypt with a PKI BW card and the mimeviewer there are also no longer problems which again might be related that the internal states where somewhat disturbed by the loop in Kleopatra.

I retested this with the current beta and It works without problems. I somehow suspect that the permanent access loop from Kleopatra caused other Smartcard operations to be canceled. Since the test setup is not really good to reproduce to for Ebo I resolved this myself.

This is very much unrelated to any GnuPG code so I can say this is resolved for Gpg4win, too.

because I did not test with gpg4win yet. And I'm not familiar enough with the code base to say that it does not need to be testet with 2.4 again. Feel free to close it and move to done in the gpgcom workboard if you think its resolved for good.

So why not resolved?

For me it is like if you open a save file dialog. You want it to remember where you saved a file the last time you saved it. But if you just browse around and cancel it, it should not store that location.

We don't change settings. We just remember what the user used the last time. That we save this information in the same file as settings doesn't make them settings. (It might be more correct to save last used keys/options in the state file where window sizes are saved since some time to better separate this information from actual settings.)