Thanks Ingo.

In 2.4 we have rG1383aa475 which does

Although I don't think this is the case here one should be aware that tests mail fail due to global configuration of GnuPG (/etc/gnupg/*.conf). There is no easy way so solve this except for running a per-test local installation of GnuPG using the gpgconf.ctl feature.

Arghh, a GPGME_DEBUG=3 which shows basic I/O preparation does not exhibit the bug.

Fixing gpg is easy but there is some bug lingering in gpgme which might be a recent regression. An strace shows

Those options where originally intended for debugging but your suggestion makes sense. I also add this to most other tools.

At the failed attempt I notice a DEVINFO_STATUS removal soon after the SWITCHCARD. This is related to the reader status file and triggered by ccid_slot_status. --debug ipc.app,reader might be a better selection of debug flags here.

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.