In vsd 3.3.6 the option is now greyed out.

@ikloecker I'd like it if we could backport the resetting of the preferences to vsd34.

Font selection dialog lets the user choose a font size, which is then not respected - can we disable selecting the font size?

Moving smime encrypted/signed mails with attachments both works with drag&drop and via context menu on gpg4win-5.0.2-beta2 @ win11 with IMAP, so I'm setting this to resolved.

gpgol.log (call trace + data)

On gpg4win-5.0.2-beta-2 @ win11 i can reproduce:

• drag&drop does work
• move via context menu
  • works for selected mails
  • does not work for unselected mails

I can't resend the mail though.

Luckily I tested T5374: GpgOL: Can't move a signed mail in Outlook from In-Mail folder to any other folder afterwards and found out, that with my current settings in gpg4win-5.0.2-beta2 @ win11 I can reproduce this every time by sending signed only mails (pgp and smime does not matter).
Regarding my settings, I only activated the security dialog:

I have no idea how to reproduce this, there is no pattern. It could as well be, that some server side thing is involved, which is not under our control.
Either I'm lucky and it just happens while the logs are enabled, or I'll try some auto loop with appium one day.

I can't reproduce this on gpg4win-5.0.2-beta2 and vsd-3.3.4.

Du we have any information on whether the CRT is used and whether u et al. is also wrong? For example due to an OpenSSL generated key?

I cannot reproduce this on gpg4win-5.0.2-beta-2 @ win11 either, so I set this to resolved.

Please briefly try to reproduce on Windows with Gpg4win 5.0.2. At lot has changed since this ticket was created so that it might be fixed already.

I cannot reproduce the empty dialog on Linux with the current build. I always see a correct result dialog for the readable file.

We use individual texts now that all follow the pattern "Detailed results of import from ..." for import from file (file name is displayed), clipboard, notepad, smart card, WKD (URL is displayed), server ("keyserver" or "LDAP server").

Note: This isn't included in Gpg4win 5.0(.2).

Note: This isn't included in Gpg4win 5.0(.2).

Note: This isn't included in Gpg4win 5.0(.2).

Note: This isn't included in Gpg4win 5.0(.2).

I stand partially corrected. Apparently, pinentry-efl also sets close_button. For Gpg4win that's irrelevant because we ship pinentry-qt (and pinentry-w32) which doesn't have this IMHO contra-intuitive behavior.

Upstream MR for reading system config files before user config files: https://invent.kde.org/frameworks/kconfig/-/merge_requests/436

pinentry-tty and pinentry-curses support GPG_ERR_FULLY_CANCELED by Ctrl-C. But other pinentry implementations have no support (only GPG_ERR_CANCELED).

I'd also like to point out that changing the error code from GPG_ERR_CANCELED to GPG_ERR_FULLY_CANCELED could cause regressions in applications.

Merge request for KMessageBox: https://invent.kde.org/frameworks/kwidgetsaddons/-/merge_requests/339

How do you want to decide whether to show two "Cancel" buttons? How would you call those two "Cancel" buttons? For decryption I can imagine that for example "Try Next Key" and "Cancel Decryption" (or even just "Cancel") would make clear what happens.

Q3 is T7650: Kleopatra: Limit width of KMessageBoxes

Any further improvements will have to go in a new ticket when we have a plan. I'll close this one.

ok, lets go with the message box.

Q1 stays like it is, for Q3 @tfry made a merge request to wrap after 120 characters. Please add a link to this.

Follow up for Q1 is T8166: Kleopatra: Add "Save Secret Team Key" button to success message after creation of "Team Key"

Relevant part from T6793: Cleanup temporary files / dirs with decrypted content:

If this definition is OK

@bernhard Thank you for the link.

In T8076#215372, @werner wrote:

If you specify a primary key the primary key shall be deleted. If there is only an offline or token based primary it can't be deleted. This is what the user requested. We can't change this because otherwise subkeys might be unintentionally deleted.

What is an "incomplete team key" - a standard offline secret key (i.e. one with only secret subkeys)?

It would be used for key creation just like the legacy options PGPKeyType and RSAKeySizes were used (and still can be used but only for RSA with different key sizes).

If you specify a primary key the primary key shall be deleted. If there is only an offline or token based primary it can't be deleted. This is what the user requested. We can't change this because otherwise subkeys might be unintentionally deleted.

I guess the behavior changed with gpg 2.4, i.e. "With gpg 2.4 (or later), ..."

Shall that be used for key creation or shall a warning be displayed when a non-allowed key is used (receive or send)?