closing and opening new tasks is the best option

works. tested with VSD 3.1.26 (gpg 2.2.41) and keyserver entry in dirmngr.conf only.

works, server can be added to dirmngr.conf via kleopatra

works with AD, too. Even with an "a" ;-)

Yes, the installation was with the unmodified Installer GnuPG-VS-Desktop-3.1.26.0-Standard.msi

works

It effects Yubikeys and ZeitControl cards (version 3.4)

We got a user report that the issue did not occur before their update from 3.1.25 to 3.1.26

works if you use a valid IP address

well, this user made a backup and it went wrong anyway ;-) See T6377

I'm sorry, I got a bit confused, it works in Kleopatra on 3.2.0, but not in 3.2.26

works

works

works: the process is canceled without any notification.

works

With GnuPG VSD 3.1.25 the Certify action is not disabled for me. Neither on Windows nor on Linux system.

works

I would ideally like a result message like "Could not connect to keyserver ks.example.org" if the server is not reachable and
"the key has not changed on keyserver ks.example.org" or "the key could not be found on keyserver ks.example.org" if one of those is true.
At least the last two not if the key was found via wkd, obviously, in that case a similar message for wkd.

works

very nice

works

works

ok, works as described.

I have tried all 3 settings (in %LOCALAPPDATA%\kleopatrarc):

AllowCertificateCreation=false

works as described.

Keyserver option is no longer shown in the OpenPGP tab of GnuPG System

works

works as described by Ingo

works

works

works

works as advertised

works as proposed by werner.

If a certificate is in more than one group, this will not work...

Hidden where?

works

Well, the picture given as example above looks exactly as before if I choose a key by clicking on it. But at least it changes after hitting return or switching to the next line, so it's an improvement.

I see no change in the reported behavior:

In T6205#163303, @ikloecker wrote:

Does the recipient know the public key that was used for encryption?

The data from the above output was additionally OpenPGP encrypted to self.
The "not compliant" message only shows when the data is additionally encrypted to a public key.

gpg: Öffentlicher Schlüssel ist 2B2F1C74FE523D81
[GNUPG:] ENC_TO 2B2F1C74FE523D81 1 0
gpg: AES256.CFB verschlüsselter Sitzungsschlüssel
[GNUPG:] NEED_PASSPHRASE_SYM 9 3 8
gpg: Verschlüsselt mit einem Passwort
gpg: verschlüsselt mit RSA Schlüssel, ID 2B2F1C74FE523D81
[GNUPG:] NO_SECKEY 2B2F1C74FE523D81
[GNUPG:] BEGIN_DECRYPTION
gpg: AES256 verschlüsselte Daten
[GNUPG:] DECRYPTION_INFO 2 9 0
gpg: Ursprünglicher Dateiname=''
[GNUPG:] PLAINTEXT 62 1663253724
[GNUPG:] PLAINTEXT_LENGTH 4
test[GNUPG:] NEWSIG
gpg: Signatur vom 15.09.2022 16:55:24 Mitteleuropäische Sommerzeit
gpg: mittels RSA-Schlüssel 930A7B212C8EC8F1729DA3F5C464074875570823
[GNUPG:] ERRSIG C464074875570823 1 10 00 1663253724 9 930A7B212C8EC8F1729DA3F5C464074875570823
[GNUPG:] NO_PUBKEY C464074875570823
gpg: Signatur kann nicht geprüft werden: Kein öffentlicher Schlüssel
[GNUPG:] DECRYPTION_OKAY
[GNUPG:] GOODMDC
[GNUPG:] END_DECRYPTION

works now

well, when creating openPGP keys with kleopatra I did not see any hints. I do not think that the issue would be vaild for password based encryption. There the common usecase is autogeneration, anyway

also, in the recipient tab the "encrypt with passphrase" option is at the very bottom and so far away from the other options that it is easily overlooked, if the window is fullsized.

it seems to be a GnuPG-VSD packaging issue, then