Can we close this?

Breaks them how?

This breaks existing 32 bit systems with the 64 bit types. Thus a test for off64_t is required which redefines it to int64_t if it does not exist.

Let me remark, that we don't need a general migrator. We only need to make sure that the kleogroups are somehow migrated. Maybe we should do this along with the change of these group files (signing, v5 fingerprints). In any case it is important to get this into vsd33

Seems it was a kernel / USB bug

RL discussion result:

This has been implemented and tested to be compatible with PGP - a looong time ago. iirc this was discussed around 1999 but might be only by private mail between the PGP hackers and me. Thus any change now might break PGP - which is still widely used (although mostly for encryption).

Oh yeah the idea to implement aliases is more than 20 years old. I guess it is even older. Thanks.

Along with the monitor we should also implement a domain selection feature.

Most things are done. Missing stuff

Thanks for the patch.

Alright: We have support for all our combined algos ky{768,1024}_bp{256,384,512}and ky{768,1024}_cv{25519,448} as well as test keys and encrypted test messages.

Another important use-case is to provide a way to migrate to a newer smartcard.

We include the ISSUER_FPR subpacket since version 2.1.16 released 2016. Thus there is virtually always a fingerprint for all signatures available.

Okay, fix pushed to master, 2.4, and 2.2. Thanks.

Nobody uses gpgtar for S/MIME

gpgme has a disabled flag (only set on the primary key) and taken from the --wwth-colon listing where it is the 'D' in the usage.