I think we should close this bug or re-purpose it to silence those warnings in common cases.

That could be fixed in src/argparse.c:set_opt_arg by adding and endptr to the strtol calls and check that only white space follows. However, there is some risk of regression with this approach. Maybe just display a warning?

Removing gpgrt because we meanwhile have full utf-8 support there.

With today's release of npth everything should be set.

The patch is part of 1.7 - please test and in case of problems feel free to re-open.

A way to generated keys in the usual s-expression way has been added. This allows us to get the keygrip for the key.

Closing due to age and because gpg4win 4 started to using the much improved GnuPG 2.4

With backup and restore import/export options all should be set for a long time. I guess this bug can be closed.

Way to old. Does anyone still uses CAcert?

Lowering priority because it does not seem to be a popular issue.

Thanks for your work. I applied it to Gpgex.

Okay, backported to 2.2.

FWIW, I posted some ideas at https://lists.gnupg.org/pipermail/librepgp-discuss/2024/000043.html . For official use in Germany we will very likely also add Brainpool curves as a replacement for the IETF curves.

The solution seems to be a newer libccid version. If that is the case we may want to include the fix also in our own ccid driver.

Please note that this is a bug tracker and not a general support channel. You would also need to write in English - we can't triage reports written in other languages.

gpg --list-packets shows this:

I need to come up with a better strategy here. --refresh-keys is a very useful command and it should do what the user expects. Maybe we can adjust the behaviour iff we detect that there is an LDAP keyserver.

No, I am not aware. I can't remember whether PGP once had such a bug because @dshaw did most cross-testing and fixing for PGP bugs. I would suggest to remove any such checks. IIRC, this was introduced by PGP 2 to speed up signature checking. 30 years ago RSA operations were quite expensive.

Although, we don't use our usual s-expressions we need to add a way to derive a keygrip from Kyber et al and also to wrap the key into an s-expression to that it can be stored by gpg-agent in its usual files. An exported new API to get the keygrip of a KEM key would be good to avoid encapsulation but for other purposes an encapsulation is still required.

That is simply because your XDG_RUNTIME is set to the same directory gnupg uses. See gnupg/common/homedir.c:_gnupg_socketdir_internal

Portable Apps are a Bad Idea because they bypass important security mechanisms. In any case please tak such discussions to a mailing list and please do not use the bug tracker for this. The audience of bug reports is pretty limited.