Thanks for the report. This is indeed a bug.

If you click on the grey question mark in the "Entry field" when adding recipients you get a dialog that lists all keys and also allows for multiple selection.

Have to test it but I think its resolved. The registry path handling is now similar to that of GpgOL and GpgEX.

Please update to Gpg4win-3.1.1 this issue should be resolved. There was a similar issue with Gpg4win 3 T2670 but it has been resolved.

We've analyzed another report of this and the problem turned out to be that with a 64 bit outlook and GnuPG not installed in the standard location it came to this error. ( T3988 )

Yes. For S/MIME we don't have the comfort to change the standards. I also would like to have a quick solution. After much deliberation with Bernhard we think that it is a good compromise from usability vs. security that we further reduce the usability for S/MIME in that we only allow (any) signed content to be displayed as a file or HTML. This is not extending the standard, not changing GPGSM but a design decision in GpgOL.
We don't have full control over our Mail client so we can't prevent the load of external references like KMail does. This suggestion is a compromise and a pragmatic solution.

Thanks for testing. A new Gpg4win release will come soon.

Argh! From the log it looks very much like another incarnation of the issue fixed in T3960 (Same underlying reason)

Thanks for your report!

Zertifikat erneuert.

I've already sent jens a mail this morning.

I understand the Problem. Your recipient formatted the reply in such a way that GpgOL does not detect that the original message is Quoted, verifies it and shows only the verified part.

But why is that the case for OpenPGP Signatures, then? The difference does not make sense to me.

Wait. Users should not have the ability in the GUI to mess with the CRL cache. That is internal / private stuff. And something for developers, so this should be removed from the GUI altogether.

I think this issue is important as GPGME should not report "Green" / Everything OK in that case and only have the EXPKEYSIG in details.

Thanks for your report. Are you sure that "Allow HTML" makes the difference?

As I link this Ticket often when talking about this limitation. Here is a short animation to show what is meant by moving but not opening a mail:

I'm not sure I understand your Problem. For me it works as it should.

The latest Version of Kleopatra has a "Notepad" View that should do what you want. E.g. If you decrypt something in there it preselects the keys the message was encrypted to when you encrypt it again.

OOooh yeee.
Ok. Didn't know how bad gpg4usb really is.
I looked into it. Gpg4usb distributes their own binary GPGME version https://github.com/gpg4usb/gpg4usb/tree/master/linbuild/lib I don't even know which version that is. They are in violation of the GPL as they don't offer the source code of that GPGME version.

I'll volunteer to look into it. IMO "Invalid Crypto Engine" points definitely to a GPGME bug and I want to know whats going on there.

This crash was new in Gpg4win-3.1.0 introduced with: dc48589b3d429d7d156c75b4e7bc784b140f40ce

Thank you for the report. I can reproduce the problem. I extended the title a bit so that its easier to find for others who might also see this.

@dcialdella Well as you are here already you can open one here. Alternatively I would have thought Ubuntu's Launchpad.

Hi Carlos,

Released today.

Both CRL downloads and the error handling / reporting is much improved in Gpg4win-3.1.1

This is resolved in my opinion. I've tested with some larger CRL's and it worked on Windows.

I thoroughly tested this again with the released versions. Works very nicely, including the timeout.

Better but still not perfect. It still can happen that it is opened in the background if you put the options dialog in the background before the window pops up. But I think that is acceptable for such a rarely used feature.

@dcialdella I've checked the Ubuntu Patches, they don't include the patch that caused the problem for GpgOL in this issue. Please report your problem either to Ubuntu or open a new issue, ideally with some instructions how to reproduce your problem.