Looks good to me on gpg4win-5.1.0-beta658 @ win11 (patch included).

Side note: I actually tested it with minimized window before and it worked, but i could not reproduce it anymore now.

Thanks for testing! Interesting that it works if the main window doesn't exist.

• Minimized (to taskbar): certificate info is opened behind the okular window
• Closed (running in background): certificate info is opened on top (works)

What happens if the Kleopatra main window is minimized?

We discussed it and decided that we want to keep the sign+encrypt option for S/MIME and single files. But for folders (and multiple files) we want to disable S/MIME signing. If people need to sign an archive, they have to create it before signing (or signing+encrypting).

Looks good to me on gpg4win-5.1.0-beta658 @ win11.

Looks good to me on gpg4win-5.1.0-beta658 @ win11:

Looks good to me on gpg4win-5.1.0-beta658 @ win11:

This issue would now be about adding a hint to the audit log for a full list of recipients, in S/MIME decryption feedback in Kleopatra.
But besides the amount of recipients, this list only shows the root certificates of the other ones:

In T8334#220258, @pl13 wrote:

The test certificates do not have a crlDP, so there is no crl check done and no dirmngr is called for this.

Patch up in https://invent.kde.org/graphics/okular/-/merge_requests/1414 that removes the finish ('cause it will not work) when reloading

Well at least the reporter was of the opinion that it worked. Depends on what one expects.

Looks good to me on gpg4win-5.1.0-beta658 @ win11.

Looks good to me on gpg4win-5.1.0-beta658 @ win11:

I don't know what you understand as "does work". For single files two completely separate things are done:

1. A detached S/MIME signature for the unencrypted file is created.
2. The unencrypted file is S/MIME encrypted.

The test certificates do not have a crlDP, so there is no crl check done and no dirmngr is called for this. (see here)
After repeating the command the issuer is looked up from the dirmngr cache. In this test case the dirmngr is not called for a crl check but for a lookup.

Moreover, for S/MIME, it will disable "combined" sign and encrypt.

This happens only, if the Kleopatra main window is open and behind Okular.

If this is only a visual cutoff/fadeout, and the content still is still displayed, after the width was adjusted.

Ah, well, the window with can obviously be changed, so a cutoff/fadeout would be fine.

A cutoff/fadeout could be problematic, if you have multiple certificates you have to distinguish.
There is some information available in the tooltip, but it might be missing some (no email in this example):

I guess cutting it off / fading it out is the only sane way of dealing with infinite long uid's ?

I think this need to be handled by Kleo ? @ikloecker

In T8018#220049, @svuorela wrote:

whattabout https://invent.kde.org/graphics/okular/-/merge_requests/1404 ?

Note: The Kleopatra window is often opened behind the other windows, and you think it does not work, so you click again and another hidden window opens. It would be nice, If this could be fixed (will create another issue for it)

The easiest fix is to enable the "exclusive" mode that we use for the notepad (and the clipboard) also for the Sign/Encrypt Files/Folder dialog. This will disable mixing of OpenPGP and S/MIME recipients (which is anyway misleading because in case of encryption the result is two separate encrypted files with mutually exclusive recipients). Moreover, for S/MIME, it will disable "combined" sign and encrypt.

it will be Sune_Vuorela_FPR_public.asc hopefully soon. and hopefully ascii armored.
I don't have the key-id handy, only the full fingerprint, and I'm not sure we should be playing scrabble with the keyId in Okular code. I'll see if I at some point can get the keyid thru.

Issue of the FAILURE split into T8340: GpgSM: Decryption with multiple recipients emits a failure, if the first pinenty is cancelled

In T8334#220115, @pl13 wrote:

The error comes from this log error message. Cancelling the pin entry leads to Operation cancelled. gpgsm exits with an error if an error was printed with the log_error function.

• The first time the gpgsm cli command is executed (without background processes), dirmngr is not started. The second time it is

In de-vs mode we have to check the certificate chain which is done after we successfully decrypted the session key. Checking the certificate chain includes a CRL check (which is done by the dirmngr).