The changes were released with Gpg4win-3.1.2.

Fix is released in Gpg4win-3.1.2

Fix is released in Gpg4win-3.1.2

The problem is complicated because we would have to parse each multipart/mixed mail before we can know that the mime structure looks that way.

Support was removed.

This was released with Gpg4win-3.1.1

Fixed with https://commits.kde.org/libkleo/79f0cb79817e44b4eab864c573740c1501e796bd

Thanks for the writeup. Maybe this could be the base for a gnupg.org/blog article.

Here is what we have now. We decided explictly not to offer a "yes I want to do something less secure" button as we think that using Unsigned S/MIME Mails is avoidable. Also we want to be more secure by default then Outlook. From a User Experience standpoint a "Yes more convenient but less secure" button basically educates users to always select that button.

I've noticed during testing that GpgOL would not send valid PGP/Inline signed only messages and also failed to verify such messages itself when special characters were in the mix.

Oops. The commits added here belong to T3975

Thanks for your report, but as JJworx already said this is sadly one of the known issues to which we don't yet have a good idea how to fix it. In T3459 there is an animation what is meant by "unselecting" the mails.

Yes, this is actually pretty high on the wishlist but AFAIK there was not yet a task for this.

There won't be anything without MDC in 2.2.8 anymore.

The best way to send signed or encrypted mail is by using PGP/MIME which is the default.

Thank you for your answer.

I've tried to prevent the download of external references selectively for S/MIME Mails. There is PR_BLOCK_STATUS but I was unable to stop the question for the user if she want's to download the external references anyway. :-/

Thanks for your report.

Thanks for the report.

In another report, it turned out to be, that with a 64 bit outlook and GnuPG not installed in the standard location it came to this error. ( T3988 )

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.

That was actually our old stance on OpenPGP encryption: For integrity we rely on the signing of messages. Remember that signing is an integral part of OpenPGP messages and does not need MIME. Some people explained that they have valid reasons not to sign and so we added the MDC.

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

Thanks. Confirmed - no crash with the beta5 dll.

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

Hi and thanks. Yes, I consistently reproduce. Here's the log file.

Thanks for your report!

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:

Thank you for the quick turn-around! I especially appreciate the difficulty of out-of-release-cycle changes.

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,

Hello Andre;

Apparently PpgOL (gpg4win 3.1.0) works well in some computers in the computer department, you have to trust God to work well with the end users of the institution, I wanted to ask when it comes out another version of Gpg4win for Outllok?

And I have another question; How can PpgOL be used on Iphone and Android phones? Is there any tool to decipher encrypted emails on the phone?

Thank you
De: aheinecke (Andre Heinecke) [mailto:noreply@dev.gnupg.org]
Enviado el: viernes 27 de abril de 2018 00:56
Para: Carlos Garcia (TI HN) <cgarcia@asjhonduras.com>
Asunto: [Task] [Updated] T3938: GpgOL: Automatic way to "force enable" it in the registry

aheinecke added a commit: rO8635193d0108: Disable OL 2013 / 2016 resiliency for us.

TASK DETAIL
https://dev.gnupg.org/T3938

EMAIL PREFERENCES
https://dev.gnupg.org/settings/panel/emailpreferences/

To: aheinecke

Cc: Carlos, aheinecke, Mak, gp_ast

This is an automated email from the GnuPG development hub. If you have registered in the past at https://bugs.gnupg.org/ your account was migrated automatically. You can visit https://dev.gnupg.org/ to set a new password and update your email preferences.

@aheinecke thanks for the post.
When you said "open a new issue" is create here or in Ubuntu forums a new issue ?
I'll do. when ?
I imagine ni some weeks will be solved but I use the tool everyday for secure text.

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

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.

I've just checked the current build to the previous one (even when I get rid of the build directories, I keep a copy of the config.log since you never know when it might come in handy).

FYI: this most recent update broke builds on OS X 10.9 for Qt, but everything else is fine.

Glad that we could locate the issue.

Thanks for the detailed information. From the log I can see the same behavior as in T3769 with the TITUS plugin. No Read event is passed to us.
I've added MailStore to the list of incompatible addons for now https://wiki.gnupg.org/GpgOL/IncompatibleAddons

Thanks for the great direction on how to debug the issue any further.

gpg 2.2.4-1ubunt amd64 GNU Privacy Guard -- minimalist p

It's possible that was one of the upstream patches they decided to include.

@dcialdella Do you have a "non standard" GnuPG / GPGME installed? What are the versions?

I have the same issue with Xubuntu 18.04 lts, and GNUPG.
./start_linux_64bit
[Error] Source: GPGME String: "Invalid crypto engine"
[Error] Source: GPGME String: "Invalid crypto engine"
[Error] Source: GPGME String: "Invalid crypto engine"

Ok so it was impossible to detect when a mail is printed and block the printing until the decryption was completed.

This was fixed with 7eed3c4c5e9f84bed0e412213cf404a18cd54358

Alright, I will create a ticket with Exquilla to see with them if this could be fixed on their side.

Thanks for your report!

Very strange behavior caused this. Outlook seems to detach from an object model call, handle a window message, and then return the object model call.

Fixed with: https://commits.kde.org/libkleo/1318d2e13764e736d29c902500c21979e99eef9c

Also confirming the workaround. Not sure whether it would have done me any justice to counter-sign the key after accepting it locally, since I only verified it against their web page. The web page is hard to find with a Google search, since Google does not turn the unspaced hexadecimal fingerprint into something that matches the space-every-four-digits format used on their PGP/GPG instruction page. Searching for "Facebook PGP key" works, though.

This task and Forum reports about CRL errors caused me to investigate a bit and we found a Bug with CRL's on Windows. T3923 which might be the root cause.

Was Okish in my last tests. But I did not fix anything compared to 3.1.0

The commit mentioned fixes the problem.

I can confirm the workaround. After importing the key from Facebook everything works as expected!
Thank you very much!

Thank you very much. It helped. I can reproduce the problem now.

Same here with Mails from Facebook, here's the log

"Invalid crypto engine" Means that there is some internal error in the signature verification / decryption.