Kleopatra has no influence on this. This does surely also happen when a new keypair is created on the command line.

Fixed. No backport needed because we use gpg4win-tools master also for VSD 3.3
@werner: gpg4win-tools needs to be updated in gpg4win master.

The file path of the group config file in line
https://dev.gnupg.org/source/g4wt/browse/master/src/resolver/resolver.cpp$171
has to be changed to the one in line
https://dev.gnupg.org/source/kleo/browse/master/src/kleopatraapplication.cpp$355 .
It may be best to add a function returning the default path to libkleo. Or to use the new path by default if no other path is passed to the c'tor of KeyGroupConfig. It's unfortunate that the path is GNUPGHOME/kleopatra/kleopatragroupsrc although the groups are also used by GpgOL and they should likely also be supported/used by KMail.

Yeah, I guess we can word this a bit less spec-like. It has more or less the same purpose as an admin PIN except that it's a 128 (?) bit key. And, if I understand correctly, it can also be used by the (admin) user to make sure they are talking to the correct card (if all cards are provisioned with unique keys). Kleopatra automatically tries to authenticate with the standard key so that we never see the prompt for the key unless we have changed it.

Backported for VSD 3.3

The additional changes were also backported for VSD 3.3

Backported for VSD 3.3