But only if you can figure out in a transaction or locked sytate whether the card needs a verify. Otherwise we have a race between changing the PIN and verifying a PIN.

This rejection could be relaxed.

Changes:

• The maximum allowed difference of the expiration between subkey and primary key is now +/-1 hour.
• If the user has no choice whether to update the subkeys together with the primary key (because either all subkeys will be skipped because they don't fulfil the conditions mentioned in the first comment or because the subkeys share the expiration of the primary key) then the checkbox is not shown. That was easier to implement and it doesn't confuse the users with a "choice" they are not allowed to change.

We need to see whether we can use the gpgconf.ctl feature also for Windows here. Registry entries for gpd and vsd also require a change.

Right. I think this task inherited the assignee from its parent task.

Done.

Isnt this more of a task for werner? But if you could create a patch that would be great, too

this should be easy since we already start gpg-agent on start

needs to be fixed soon. But we don't have a tag for Gpg4win 5 or whatever we call a kf6 based gpg4win.

This can be tested with Kleopatra by configuring an invalid keyserver and then updating an OpenPGP certificate.

Instead of "The key hasn't changed." Kleopatra now displays "The update was skipped because no keyserver is configured."