Tested with VS-Desktop-3.2.93.33-Beta, works!

Tested with VS-Desktop-3.2.93.33-Beta:

Tested with VS-Desktop-3.2.93.33-Beta, where everything necessary is backported:

I need to evaluate this. However, what we can can do already now is to ignore all Auth keys - they don't matter at all and it is pretty convenient to have Brainpool primary and encryption subkey but an ed25519 auth subkey on a card. That is because ssh does not support Brainpool. We should show such a key (i.e. Yubikey) as compliant.

This needs Werner's input.

Please remove the any configuration file changes from kwatchgnupg. That is not a good idea. Launching kwatchgnupg is
a debugging aid and not a regular operation and thus the user can also enable debugging selectively with kleopatra.
kwatchgnupg should listen on the standard socket socket:// - for Windows we don't yet need it because there we don't have sockets anyway. Or well, eventually we will have same but that requires work in watchgnupg and gpgrt for the logging stuff.

2.2.44 seems to be released. Is it correct that this issue shows as "open"?

We discussed a different file format for group definitions. It's based on gpg's --with-colons format.

current plan after discussion today is as follows:

Should also work in VSD 3.3

Should work (if correct path is set in qt.conf).

Okay. Let us split it into different tarballs and repos. We will bump the gpgme core version to 2.0 to indicate this split despite that there will be non-ABI/API incompatibility. C++, Qt, Python will then go into separate projects. The old common List stuff will be kept in gpgme core for now. The gpgme core sticks with autoconf stuff but for C++ and Qt cmake style will be used instead.

The Down button should be disabled if no suitable certificates are selected. That may not be the case (in Qt 5) because Qt seems to add disabled rows to the selection and the work around is applied when the Down button is pressed.

In T7019#190282, @aheinecke wrote:

I would vote anyway for hiding the smartcard tab if it has no information, just so that we are not confusing, I can otherwise imagine support questions like: "It says something about smartcards, do I need such a smart card?" As smartcards for crypto is not something generally known by users, i assume.

Just thinking about this, we have at least one customer configuration that uses KXMLGui to hide all smartcard actions and the view. And one other that disables certify actions everywhere. We need to check that this still works with the new details view.

Without administrator rights it does not work for me, since it then cannot write to %PROGRAMDATA% to install the VS-NfD mode config files. But the only thing for "does not work anyway" that I know and could quickly see is that "IPC connect call failed" problem with GPGEX (which we are planning to remove / replace anyway). So I don't think it is very important to remove this and addtionally we do not know if this is something that is used, we have offered it from the beginning but have no data if our customers use it. We can suspect that we would have seen more support questions about the gpgex error if it was widely used. But I always thought that the "only for me" installation option was useful for some use cases.