I've created a global trustlist.txt at C:\ProgramData\GNU\etc\gnupg with an entry for the RootCA for Werners QES key with the qual keyword. (The local config would not work, according to the man page.)

Adding a new column to the layout is now remembered.
The with of the newly added column (Key-ID, all others are shown by default) is not set to the width of the content. But I think that is ok, one can increase the width manually and that is then remembered.

I am surprised that the solution with the separate tab was chosen… Looks like this:

works in Gpg4win-5.0.0-beta476

Ok, only 2 confirmations after the one above any more (for a standard key), they look like this:

Ok, my fault, I missed that in the beginning there was logging in the background which consumed gpg's error message.

If no logging is running in the background (that's something that often trips me…) on consecutive runs:

with Gpg4win-5.0.0-beta476

Yes, Kleopatra quits again with the beta from yesterday:

@timegrid I would not tag this ticket with LDAP, as it is not LDAP specific

State in Gpg4win-5.0.0-beta446 and vsd 3.3.4 is this:

This is really weird behavior. It seems other secret keys in the keyring may also change to "undefined" validity when the certification is done with another key. And something about the key which is certified is important.
But it can also happen that it is enough to just import a secret key without certifying anything with it for it to be shown as "undefined" validity.

This task is obsolete as we do no longer use the Temp directory for encryption (I believe since vsd3.3.0/gpg4win 4.4.0). Instead the file is written directly to the target location with the ending ".part". It is renamed there after the encryption is completed.

The aim of this ticket is to map the message in Kleo for the corresponding gpg case to the "Not found" error in gpgsm and thus show the other message instead.

ok, yes, looks like this was not thought through. How about "Sign/Encrypt settings"?

This relates to T7917: Check for revocation of the ADSK's original subkey

The expected behavior is that only "Ted" (the key from where the ADSK originates) is listed, regardless of ADSKs, on every listing.
Because for regular keys there can only ever be one, "gpg -k" shows always only one key.
Subkeys which are ADSKs shall therefore never be listed with this command.

Tested with Gpg4win-5.0.0-beta446, identically to the procedure from the description:

ok, then this ticket will be for improvement of the usability.

This is still the case in Gpg4win-5.0.0-beta413

It is not entirely clear what was meant here.
Probably it is about a command line option for opening the group config from Outlook/GpgOL or KMail. Which would be useful.

This was resolved some at time in the past

@svuorela Isn't this done already for KF6?

@werner : is this already testable?

isn't this done?

Tested VSD 3.4: Fingerprints can be copied in the certificate list with select and CTRL+C. CRTL+V then will insert the fingerprint without spcaes

setting this to resolved, werner already tested this

we haven't seen this in a while…

I believe the reason was simply that we wanted it short, "Upload successful." sounds better than"Publication successful." and I associate keyserver more with upload than publication. Furthermore "Certificate successfully published" has the disadvantage of being correct only for the upload of one certificates, not multiple. So you'd have to have case differentiation.

I would say this is done.

Additionally to the issue Andre cited years ago, we also did some changes to fix other how signed/encrypted mails are shown, which are also relevant for the inbox. This should be fixed.

This is a duplicate of T7833: GpgOL: Security level 2 shown for manually imported and certified cert