I do not understand why there should be an integer overflow:

For OpenPGP cards >= v2.0 there is no PUK due to updated ISO standards but we use the term in Kleopatra for the Reset-Code.

This is not a bug. We changed it as a convenience for some Emacs users.

Sorry, no. The change is too large to back port it w/o risking a regression. As mentioned in T6481#170366 I don't consider this a bug. We are anyway working towards version 2.6 which will be the next LTS version.

Although it is implemented in gnupg-2.2 we should add another feature: Iff this option is configured, gpg shall try to load the requested key from LDAP in the same manner as it does for a trusted-key.

This should not be configured in Kleopatra but an option to gpg because this is a core crypto functionality. Thus is now a gpg task.

Well, but if the padding is indeed limited to 7 bytes the fix should be applied anyway.

Can you give a hint where there is a buffer overrun in the first patch? Padding limit might be correct but I can't see an overrun.

Thanks for running the analyzer. We need to have a closer look at the suggested fixes. For example initializing a variable needs a reason and should not be done as a general precaution because that may hide other errors.

Back in the ancient days we allowed to dlopen algorithms so to avoid patent problems in certain countries.

Actually we are using gpgme already for 64 bit Windows; but statically linked.

Pretty outdated, but I add it nevertheless to 2.4
s/gnupg-2.4/po/nl.po: 1320 translated messages, 625 fuzzy translations, 268 untranslated messages.

Done for gpg. Needs to be done for gpgsm.

Looks good to me. Thanks.

Please, we need a fix here for 3.3.

I still spotted a grammar glitch in corrections. Thus if we apply this we need to proofread it.

Yes, I think we should support this. Also X448. Thanks for the report and the samples.

I noticed this recently too on some boxes. Thanks for the good decription. This support for pkg-config style .pc files for our config scripts seems to be a never ending story. The alternative name for libgpg-error-config does not make it easier.

pwd is not a standard Windows command. It is availabe in powershell but there I get

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.