Should be fixed.

Phew! This bug has been with us for more than 20 years unless gpg's behaviour has changed only later.

Using -o signedtext.txt fixes the problem. Unfortunately, gpgme does

      err = add_arg (gpg, "--output");
      if (!err)
	err = add_arg (gpg, "-");
[...]
      if (!err)
	err = add_data (gpg, plaintext, 1, 1);

i.e. it tells gpg to write the output to stdout and then reads everything from stdout as plaintext.

In the group dialog I can not cycle forward with Tab endlessly through the not-greyed-out buttons of the window because the focus gets stuck in the bottom row. There "Revert" is included in the cycling, which is not correct, since it is greyed out. With Shift+Tab, cycling backwards works as expected.

On windows the main window looks ok with high contrast mode black. But with dark backgrounds some items in other windows are not readable:

The error was changed to "Bad data" which should be more appropriate.

In T6617#173396, @werner wrote:

What we have here is a clear text signature followed by a public key. If you run this with
gpg -o signedtext.txt --status-fd 2 signedtext.txt should only receive "bar" and not the key listing. If that is not the case something would be very wrong.

This works on Linux with KMail and with Claws (although with Claws the attachment is added twice).

works on windows, too

This issue should be tested together with T6621: Kleopatra: Remove "in n days/weeks/months/years" input from Change Validity Period dialog.

I have also further unified the handling of the expiration date when

• generating a new OpenPGP certificate
• changing the validity period of an OpenPGP certificate
• certifying an OpenPGP certificate

I didn't check with a CardOS / PKCS#15 card but as the solution is not card specific, checking with another card should be sufficent.

Small summary onf the recent progress, I made:

I would change the error to GPG_ERR_BAD_DATA .

This is now done with https://lists.gnupg.org/pipermail/gnupg-devel/2023-July/035401.html and https://invent.kde.org/pim/messagelib/-/merge_requests/138

I agree.

Pushed the change to libgpg-error.

We now show an error message when the user tries to set an invalid expiration date when changing the expiration date. Additionally,
the configured minimum and maximum validity period is now taken into account, i.e. for changing the expiration now the same rules are applied as for new certificates.

Thanks for the pointer! I'll see how I can do what ecdh_param_str_from_pk does in gpgme.

The relevant commit is rGc03ba92576e34f791430ab1c68814ff16c81407b