Yes most definetly I am looking it at next

works, Gpg4win-4.1.1-beta295

fixed

This is basically working as intended by gpg --quick-set-expire. With a first call of gpg --quick-set-expire the validity of the primary key is extended. With a second call of gpg --quick-set-expire with third option * gpg is asked to update the expiration time "of all non-revoked and not yet expired subkeys".

the option works

Closing. A small change in Kleopatra (T6472) should help to avoid using this hack in common cases.

Setting priority to high because this should be fixed before the next release.

I have checked that we now switch back to openpgp (if necessary) after every use of ReaderStatus::startSimpleTransaction and ReaderStatus::startTransaction. The only uses of those functions outside of subclasses of CardCommand are by PGPCardWidget for which switching back to openpgp isn't needed.

Why can't we keep the signed int? Do we ever need such a long timeout. We could for example define -1 as use default timeout.

assuan_sock_connect_byname may be extended to change the third argument (now int reserved) to unsigned int timeout.
It's a kind of API change, but ABI wise, the impact is minimum.

in gpg.conf

This has been fixed for gnupg24 and gpg4win.

!ebo: Did you set a log-file into gpg.conf or common.conf ?

This works, basically.

Note that this change has the inconvenient consequence for the users that they will have to (re-)enter the PIV Authentication Key for each operation that requires authentication, e.g. for each write operation (generate key, write key, write certificate), because switching to openpgp seems to reset the PIV authentication.

works now, Gpg4win-4.1.1-beta295

works

works with Gpg4win-4.1.1-beta295

The workaround works.

I learned that Unix build environment needs Wine emulation (with winepath) for MinGW host (when uninstalled executable should run correctly).
https://www.gnu.org/software/libtool/manual/html_node/File-name-conversion.html

I imported only a secret key file generated by "Backup secret key"

Fixed for libgcrypt, updating copyright notices and license files.

Did you by chance import the public key file and the secret key file for the same certificate?

Note to self: This might happen because the key is/was expired.

works. Including "Verschlüsseln".

See T6474 for the remaining issue.

The readability would be much improved by adding named constants for the magic numbers 2 and 4.

@ikloecker Thanks for your comment. I put a comment in the commit.