I was able to reproduce this when I forwarded the mail after opening it in a new window. Somehow that appears to influence it.

Closing this as the moving problem was fixed.

I guess you are the only person who does it. But yeah. I agree that it should be fixed.

I agree with @dkg here.

When doing a "gpgsm --with-validation -k foo" (assuming you have a cert foo) gpgsm now goes into a loop and prints the certficates that match "foo" over and over again. I have not tested if it was caused by this change but I think it is likely.

Smartcard support is a big advantage of using the GnuPG backend and it should work of course.

I imported 39 certificate files at once with Kleopatra with about 700 certificates and it worked. Took a long time though so It would be nice if Kleopatra would show a progess indicator or some indication that the import is running. But this is a different issue.

Or a better tl;dr; When you send mails without "inline" option everything is fine and standardized. The problem is that the old version of GpgOL that your college uses is too stupid to handle this ;-)

Yes your colleague should or basically needs to upgrade. 2.2.3 is very outdated. There are security issues that were fixed by then etc.

What client does your colleague use so that you have to use PGP/Inline?

The last lines that the process currently holding wrote in the log:

To reproduce this issue I started Kleopatra with an empty GNUPGHOME and imported 10 S/MIME certs at once (which spawns a gpgsm process each) with enabled logging.

Thanks for the explanation.

As this update lists multiple issues and following fixes for them, maybe it was resolved by Microsoft?

As I want to keep this tracker clean I would say this is a Wontfix at least until someone (DKG?) provides an argument what would be gained and why we should do this.

Mmh no. This needs to go into the resolver. If autoresolve is disabled we also want to have that functionality. Having the ca config in libkleo would also help to use the same values in Kleopatra for a CSR.

This should resolve it.

Well there is nothing specially pythonic about it, it just includes the dirs and not the files:

Merged. Thanks again for your work on this.

Thanks for the explanation. That addresses my concerns.

That makes sense to me. So I've now moved the -Wno flags out of the maintainer mode conditional but left the parts adding warnings in the maintainer mode conditional.

Good to hear this request from someone else, this gives it more priority :-).

Thanks for the report. This is annoying me, too when doing release builds.