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.

This is just another sympton with the same root cause. Therefore I have closed this as duplicate.

Interesting. I didn't even know that this feature exists.

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

I already mentioned the exact same thing in T7004 and this user also used the wiki style of the bug report form at first to report a bug. That is why I took the extraordinary step of blocking him.

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

This doesn't work reliably for the key list in the smart card view for TCOS/NetKey cards. After a few starts the "Key ID" column is reset to the default width (which is too narrow). The layout does survive a restart directly after I changed the column size. I haven't noticed a pattern when it's lost. I know this isn't really helpful. I'll open a ticket when I find out how to reproduce the problem.

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.