Gpg4win-5.0.0-beta32
Works!

Ok, then this will not be included in the VSD versions until we switch away from gpg 2.2

21f7ad563d9b was not backported to gnupg 2.2, so this can't be done yet

It's missing a check for the required gpg-2.2 version. I will add that

If you encounter real world certificates with these parameters we can bump up the priority.

In VS-Desktop-3.2.94.481-Beta the feature is not available in the context menu in Kleopatra.
So in VSD 3.3.0 this will be missing. What works is disable/enable on the command line and Kleopatra will then not list a disabled certificate with most filters.

I think I can understand you, too much complexity.

See this comment which is related to T4538:

Hm, "Names for the certificate" seems wrong to me. Shouldn't it better be "Names in the User IDs [of this certificate]"? I would leave of the part in [] as redundant. Likewise for the mail addresses.

Thinking about this some more, i came up with some more ways of showing some nice-to-have information in the tooltips:

https://invent.kde.org/pim/kleopatra/-/merge_requests/355 makes both components use the same tooltips; we can then change both when we decide on what exactly to show in the tooltips in general

Fixed in 2.5.2.

it would be best to add an API to gpgrt to iterate over registry entries.

Works. Tested with VS-Desktop-3.2.94.474-Beta and Gpg4win 4.4 by moving only the signature key to a smartcard and then changing the password of the certificate via the context menu.

This was now added as disableAutoPreview (the option was renamed after 26c2fc196bb73d9bd96c91ea7cc12679d925b376 )

Since codesigning for all dlls was added this is fully resolved.

(ignore the last commit, I assigned the wrong task to it)

Here are changes for gcry_md_open and its friends.

My idea in https://dev.gnupg.org/T7338#195529 doesn't work well when a function call is done multiple times.
Assuming SUCCESS, and marking all non-compliant places in the code works, and it would be good because libgcrypt so far maintains non-compliant path with rejection.

Or maybe not. I just did 0.11.0 (T7449) and will do more releases if there is demand for it or we have collected enough patches.

Pushed the change for adding hash tests in rC7faf542f1573: fips,tests: Add t-digest.

Gpg4win 4.4:

It seems that the internal API (as of 2024-12-06) is not enough.
Now, we have _gcry_md_hash_buffer function with the new FIPS service indicator.
It's used for public key crypto, too.
The compliance for hash function is a part of public key crypto, but not all.

A change for gcry_md_hash_* functions are pushed by rC3478caac62c7: fips,md: Implement new FIPS service indicator for gcry_md_hash_*..
It doesn't have tests with FIPS service indicator yet.

Better a new ticket for the rest, see T7441

A workaround exists with the new option --ignore-crl-extensions.

New external API is by GCRYCTL_FIPS_SERVICE_INDICATOR and/or the new macro gcry_get_fips_service_indicator.
This change is pushed by rCf51f4e98930e: fips: Introduce GCRYCTL_FIPS_SERVICE_INDICATOR and the macro.

New internal API is introduced with T7340 by the commit rCe1cf31232825: fips: Introduce an internal API for FIPS service indicator.

Change is pushed by rCe1cf31232825: fips: Introduce an internal API for FIPS service indicator.

Looks like there's something not correct in the completion model. Or we use different criteria for showing the blue "i" (as "information") which doesn't make it better. Reopen?

Tested Gpg4win 4.4:
Interesting, when you search for the UID, it looks as before, with the green check mark:

I think this is resolved. In the Sign/Encrypt dialog we now offer the individual user IDs instead of the certificates, i.e. the two user IDs of the Udo certificate are both offered and one should be listed as certified and the other one as not certified (if one is certified and the other one isn't; for me both user IDs are ultimately trusted).

Closing this as duplicate of T7405. That ticket has the better task description as it was made after discussing offline how it could best be done.

closing this as duplicate for the improvement part, the support part is solved, anyway.

Interesting. Just a few days ago I noticed that Kleopatra creates a new tab with the imported certificates except when the import is done via the notepad (or via the clipboard). I guess we could add an option to open a tab with the imported certificates to the import result window.

Done for 2.5.0.

Done in 2.5.0.

Fixed in 2.5.0.

Fixed in 2.5.0.

Gpg4win-Beta-94: ok

With Gpg4win-Beta-94 now all is fine, even own deactivated certificates are now shown (using the "Disabled" filter) in bold font

Name of the window is now "GnuPG Configuration Overview" and "gpgconf -X" is preselected and executed in the window.

Latest changes backported for VSD 3.3

Backported for VSD 3.3

I like it better than the very long tool tip.

Changed in https://invent.kde.org/pim/kleopatra/-/merge_requests/316

Hm, probably I would be for the html-tags, then. Is there an example where one could see how narrow tool tips really get with that option?

We shouldn't have to add explicit line breaks. Explicit line breaks will lead to bad formatting (German: Flattersatz) for people who use huge font sizes (a11y!) and Qt will wrap long tool tips so that they won't become wider than the screen. Alternatively, we wrap the tool tips (in the code that sets the tool tips) into <html> tags. Then (for whatever reason) Qt will make the tool tips much narrower. (Some people think too narrow, but we have to die one death.)

Fixed in https://invent.kde.org/pim/libkleo/-/merge_requests/163

setting this to open for the small fix in the tooltip.
I suggest as new text:
"Disabled certificates are not offered when selecting a certificate to sign with or to encrypt for.\nThey are not shown in the certificate list with most filters."
And I think there should be an additional newline somewhere, as I was shown a much too long tool tip. The German text is not that much longer…

Removing the appearance filter won't fix own disabled certificates not being bold; the problem here is that the "My certificates" filter doesn't trigger at all anymore for disabled certificates

Yeah. so lets ditch that appearance filter. But that's for ticket T7217. So I'm setting this ticket to done for 4win.