I guess no. But yes, am also annoyed by the default for "insert card" - sometimes several times a day. We should really fix that.

Does this relate to which button is selected by default by a pinentry prompt for inserting a card? I am very annoyed by the default for it being "Cancel" as I can't just press enter after inserting the card, but have to tab to or use the mouse to press the OK button.
It would be great if the default for the card insertion prompt would be OK.

On gpg4win-5.0.2-beta-2 @ win11 i can reproduce:

• drag&drop does work
• move via context menu
  • works for selected mails
  • does not work for unselected mails

Upstream MR for reading system config files before user config files: https://invent.kde.org/frameworks/kconfig/-/merge_requests/436

I cannot reproduce this problem anymore with Gpg4win 5.0.1. The bug seems to have been fixed in the meantime by changes made upstream.

We should also change the "donate" button to Gpg4win then and the text to "voluntary payment".

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

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

Looks good to me on parallel install of

1. gpg4win-5.0.2-beta2 @ win11
2. vsd-4.0.0-beta1203 @ 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.

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

@werner said the reading order should be like on the page https://gnupg.com/vsd/kleopatra-settings.html:

Tested with Gpg4win 5.0.2 (Beta):
Registry settings SOFTWARE\Gpg4win\Kleopatra\<config group>\<config entry>
works (I used [CertificateCreationWizard] EMAIL_placeholder for testing)

This is nothing we want to do in Kleopatra. The "Force" button will be removed shortly even for MDC error.

This has been specified in 1997 by PGP 5 for a good reason. We talked often enough about this and it does not help to repeat your ideas over and over again. RFC9580 specifies a different protocol than OpenPGP as specified by RFC2440 and RFC4880 but alas grabbed the name OpenPGP for this.

b) For non-confirmed keys it returns broken OpenPGP keys (ie. without a user id and thus without important information)

Thank you very much for yours answers, explanations and effort!!!

Yeah sure.

In T8101#213455, @werner wrote:

You need to use a current Windows version (and not Windows Server 2016)

keys.openpgp.org has two problems: a) it is a centralized service due to the requirement to confirm mail addresses. b) For non-confirmed keys it returns broken OpenPGP keys (ie. without a user id and thus without important information). For these reasons and the general problems with the keyserver-(networks) there is no more default.

I'm surprised that nobody did detect these problems during the long beta phase...

Please do not use the portable installation - it is dangerous to use it. We will eventually remove this option.

Should work now.

This was fixed in Qt 6.10.0 by adding compatibility code that's "hidden" behind a compiler flag, i.e. we just need to enable this compiler flag. See https://codereview.qt-project.org/c/qt/qtbase/+/629255 for details.

For the time being I "upgraded 5.0.1 to 4.4.1 (in the new directory), and then Kleopatra started again.
When upgrading that installation again to 5.0.1, Kleopatra does not start (same error message as before).

Also: When I click "Abort" ("Abbrechen"), the dialog disappeared, but the main windows does not show any progress: Specifically it does not abort.
I had to press "Abort" ("Abbrechen") in the main window; then the upgrade aborted.
When retrying (and confirming that I don't want to install as Administrator (actually I cannot)), the proposed target directory still is "C:\Program Files\Gpg4win".
When locating the previous installation directory (it seems it was a subdirectory of %USERPROFIL%\Downloads) the upgrade succeeded, but Kleopatra fails to start.
It wants a bin\Qt6Core.dll, but in the bin directory there is only a Qt5Corew.dll dated " 14. ‎Juli ‎2023, ‏‎13:23:40".
When retrying the installation/upgrade it announced to upgrade 5.0.1, but then did seemingly nothing (I guess as the version was estimated to "be current" already).
It seems some "reinstall/repair" option is missing.

We forgot to update the tooltip when the default keyserver was removed in gpg 2.5.3. This has already been fixed in the meantime. Sorry for the inconvenience!

Meanwhile all executables are signed.

The blue Kleopatra icon is now used for the Windows builds of Gpg4win and GPD and for the corresponding AppImages.