config file: Sorry, I got confused, it has to be %APPDATA%\GnuPG VS-Desktop\kleopatrarc in this case (VS-Desktop-4.0.90.1203-Beta), of course. And this one works.
Registry entry SOFTWARE\GnuPG VS-Desktop\Kleopatra\CMS\SaveCSRAsPEM does not work, though. But this is a separate issue, seems all Registry entries do not work in that build.

• config file: According to T7717: Location of qt-application config files %APPDATA%/Gpg4win/kleopatrarc should work.
• registry: According to T5707: Kleopatra: Use windows registry additionally to config files this should be SOFTWARE\Gpg4win\Kleopatra\CMS\SaveCSRAsPEM now

Works with VS-Desktop-4.0.90.1203-Beta when putting this in C:\Program Files\GnuPG VS-Desktop\share\kleopatrarc
CSR is then saved as .pem file with ascii-armored content.

Done and backported for VSD 3.4.

So ok, go ahead Ingo with your plan in https://dev.gnupg.org/T7502#213972

As the migration to keyboxd will happen not too far in the future, we'll close this ticket.
Keylisting should meanwhile already be faster due to other changes.

Closing this as invalid.

I tend to agree with keeping it short and close to the wording we use for normal public key imports.

Ok, the behavior in gpg4win-5.0.0-beta413 @ win10 is the same (< 1s).
I can also reproduce the same behavior in other windows dialogs, e.g. in the explorer (changing the location address, clicking on the search input field).
So i'd also say, that this is a virtualbox or win issue and would just close this as invalid without further testing?

I'll also retest this with gpg4win-5.0.0-beta413. I think, this bug was different back then (no need to do it quickly). If it's gone there, too, it might have been a virtualbox or win bug. If it's still there, it might hint at qt/kde.

It turns out that the problem occurs if one clicks with the mouse quickly (< 1 s) after typing a character.

I was too fast with closing this, seems it is reproducible under special conditions. But not by me, here it works.

Me neither, neither on Win10 or 11. I tried the original description and https://dev.gnupg.org/T7943#208784

I can still reproduce this with gpg4win-5.0.1 @ win11

I cannot reproduce this with the released Gpg4win 5.0.1 on Windows 10 (VM).

Done.

For highlighting the cell see T7954: Kleopatra: Highlight focused cell in tables

Backported for VSD 3.4

We decided to backport to VSD 3.4 because it fixes an accessibility issue.

Backported for VSD 3.4

We decided to backport to VSD 3.4 because it fixes an accessibility issue (wrong tab order).

Fixed.

The fix also fixes the wrong tab order of the Close button. (See T8125: Kleopatra: Wrong tab order of "Show Email" button for the same problem concerning the Show Email button.)

Regarding the above comments:
Currently, the Show Email button is never shown in the notepad and the Close button (as X) is only shown in the notepad. So, in the notepad there's only Show Audit Log next to X. And elsewhere there's Show Audit Log and, if applicable, Show Email below.

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

Please add the hint you mentioned.

Changing the position needs some more thought. There can be up to four buttons displayed next to the result:

• Force decryption is shown if decryption failed due to a missing integrity check (MDC)
• Show Audit Log is always shown (unless retrieving the audit log failed)
• Show Email is shown if the decrypted content is something that can be opened in the mail viewer
• Close is always shown in the notepad

"Show audit log" is already a button (probably changed for another ticket). I'll look into the remaining points.

I have implemented this for all tables in T6568. I missed this extra ticket. I'll merge it with T6568.

The workaround is ready for testing. Kleopatra shouldn't show duplicate LDAP servers in the settings dialog. As a side effect global ldapserver entries should no longer multiply in the local dirmngr.conf each time the LDAP servers are changed, but one copy of the global ldapserver entries is still written to the local dirmngr.conf.

Backported for VSD 3.4

Done.

The fix is only a workaround, the duplicate entries are no longer shown in Kleopatra, they still exist and multiply on save.

How about "Certification includes that you check the fingerprint against a trusted source."? "Means" seems wrong to me. @hej, please comment

ok, lets do this. I'll update the description

I'm fine with just dropping it.

One doesn't even need a global config file to reproduce the duplication.

I'm okay with omitting the list of suggestions for shared secret keys. The person distributing the key should have told the recipients how to import and certify them properly.

Also backported for VSD 3.4.

Now also available in Gpg4win 5.

Ready for testing in VSD 3.3

How about changing the text after sentence two simply to:

Do we agree to drop bolt font for QES certificates?
Will we change this for VSD 3.4?

What about always using PEM for all generated CSRs? As far as I can see, gpgsm command line always uses PEM when generating CSRs.

Backported for VSD 3.4