Priority Low as it's partly a question and We can't reproduce (for me keygen is reasonably fast)

@PaulJ this sounds like a different problem. For you it does not show. In this report the pinentry open's in the background for file sign / encrypt.

I'm giving this normal priority because I can't reproduce this.

I'm closing this as a duplicate of T3459 even if this bug is older we used it to discuss side topics.

Hi, sorry this is a known issue. To quote the README:

I have installed the update now @JochenSaalfeld and will observe the behaviour over the coming days.
Somehow my Outlook in combination with the plugin messed with the registry. I could only permanently re-enable the plugin after removing all related registry entries in HKEY_CURRENT_USER. Otherwise it would not load on start anymore even if activated by me.

Thanks for the test!

Hello Jochen,

After having a look at the code base I guess this behaviour is intentional.

It could depend on the formatting in Outlook (changing hyphens etc.), e.g.
-----BEGIN PGP MESSAGE----- looks sometimes different in Messages.

Great, I'll do it :)

I fixed the problem with multiselection that caused a very similar log for me. The fix is now in 2.0.4-beta6

I'm pretty sure I've fixed it. It would be great if you could try with the latest beta (currently 2.0.4-beta6) from https://files.gpg4win.org/Beta/gpgol/ (just replace your gpgol.dll in the gpg4win/bin or bin_64 folder with the one from there. To confirm that it's fixed.

As I reported this myself and fixed it. -> resolved.

Well the key resolution handling and dialog needs some love. Thats on the todo. But this issue here can be resolved as the op says.

I think this can be resolved.
GpgOL in gpg4win 3.0 supports HTML Mails. There is no extra setting which variant is preferred for multipart/alternative mails because GpgOL reads that setting from Outlook and prefers the same that Outlook would prefer.

I can reproduce a similar behavior when selecting all mails in a large folder. This was for T3433 It's not a loop it's just a huge load of "Read" events Outlook sends GpgOL and GpgOL looks at every mail.

Thanks. I'll give that a go. The only issue here is that it takes quite a long, random time to happen so chances are a successful fix is one where I never revisit this ticket :-)

Indeed indeed. I can reproduce and see that GpgOL is very active when many mails are selected. This is a regression, it worked with an older MIME enabled version. I'll look at it.

The symbols are coming from the message class and are only updated when the mail is viewed and afterwards unselected. It might be that Outlook sometimes does not update the symbol when the message class changes after the message has been read once.

Somehow I expected such a report (too many open fds). We will need to replace our select based code by poll. However, I think this is more related to T3529.

I think I fixed your problem. We had a similar problem in the past and the fix there was not to invalidate the UI (Update GpgOL's status button) so quickly when the selection changed.

Hi,
thanks for your report. We already have this on our todo with high priority: T3514
I'm resolving this report as a duplicate.

@simypat Please try to move away GnuPG's data directory ( %APPDATA%\gnupg ) and start GPA again. That should fix it as the problem was a corruption of an internal database that lives in the Home directory (and is not removed when uninstalling).

According to our tests and the Message board this is fixed.

THANK YOU! Once you push those changes, I'll see about back-porting the patches to Debian stable/Ubuntu LTS.

Thanks for that assessment.

What happens in the log:

Thanks for your patches. I decided to do this similar but I need to take several branches in account.

The attached patches make the necessary changes to libgcrypt and gpg-agent. A word about my change to libgcrypt. Since all of the *_secure allocation operations were hardcoded to set xhint to zero, I simply replaced that hardcoded value with a static variable. In the patches I have some sample documentation for both changes. My scheme skills are quite old, so I did not write a test case.

Please do not post warning. They are called warnings for a reason.

Please ignore them.

The new tool is called txxmpp.

Here is the test case that I wrote a while back (Follow-up to Crashes with gpg-agent 2.1.18). It is written with bash in mind and creates a stand-alone GNUPGHOME directory with a pinentry routine that supplies the password (I guess I could have preset the passphrase) and then starts 200 concurrent gpg decryption requests. With GPG 2.1.18 and up, this usually exposes the out of memory situation very fast.

Fixed for 2.2. Thanks.

All source code which makes up the installer is distributed by us. Signed by one or more of the core developers.

I disabled your account. If might be possible to remove mail addresses from the DB but I don't known how to do that.

Yes, I downloaded from "gpg4win.org".
Notice that the SHA256 from VirusTotal and gpg4win.org for "gpg4win-3.0.1.exe" are identical.
SHA256: f05e5d272a794002149effc516f4b32f62fa575563f632b084bd044017b1206f

I can't reproduce I sent myself serveral messages in which i pasted a PGP Message and they worked. I tried both HTML and Text plain messages.
To be sure I also installed Gpg4win 2.3.0 and sent myself a message with that and that also worked :-/

we uninstalled the old version, restarted, installed the new 3.01, and it still does the error

Thank you for your detailed report and the description for the reproducable setup! We will investigate in that issue!

Nevermind, I did not realize that passwd does not only operate on the selected key but on all keys (subkeys) in sequence.

I've sent an email from Outlook using version 2.3.3, to myself. What I see in Outlook with version 3.0.1 is:

-----BEGIN PGP MESSAGE-----
Version: GnuPG v2
hQEMA6jFcgdYY5bVAQgAhWTqExXJVk3aPC5rKYFUeb0NSR+TtChjBzxBrFzQ5qDr
trJiT6o7XoFYDKwdJFXMv81Zcetsu/dOq3dPoCpaQDAtna8xshJDogsx7bOV5bvO
9kLzegZqUk4RzAJLCOTkIISh/Qi6o6kXL4+Iwm17FKfVb0MSAjmrOV50SevrKpD+
PxEYr7BJHRwA9HcYMCb1tvao74AFShZV2olEuwuGvF2nuuqTl6MngKI0Qhteds3F
B6MPOckhHvOCLr3u1z7ld+svggaVFhPyTbXuGxTXAHyieeUr0yf+p4UufdTj3XTn
L/ZeK7l0TKJykbWZmFfZFDClyEDvQx1Vq7ggLuIbh9I/Ab/LkshjC+QGFmfpVaH/
D03ZQv+RStnlI3ZVWvWsAxsaWp/hEsP4RHkmVQXhI4YeRBw1e6TeXzvTvMidjnBC
=oLiX
-----END PGP MESSAGE-----

In the GpgOL ribbon the button shows a question mark and an "unsafe" label.

I tried to remove the passphrase on my authentication subkey but the same issue seems to still be present in version 2.2.2.

In D448#3614, @werner wrote:

The rest looks technically okay. My French is too limited to say anything about the translation, though.

We both came from Gpg4win 2.3.2, WE BOTH upgraded to 3.0, as a consequence WE BOTH were unable to decrypt mails once encrypted with Gpg4win 2.3.2 (and actually way older Version of Gpg4win): Please also see https://wald.intevation.org/forum/forum.php?thread_id=1781&forum_id=21&group_id=11 for further description of the issue. Now I AM able to decrypt these mails, my collegue is not (even she also is on 3.0.1).

So to get this straigt:

Unfortunately not, since I am able to decrypt them now (also encrypted with GPG4Win 2.3.2) AFTER the upgrade from 3.0 to 3.0.1 (we both went from 2.3.2 to 3.0 to 3.0.1).

In T3419#106033, @cdeibert wrote:

Hi, VERY odd: My collegue has the exact same installation and environment (actually software deployment-based), she still is suffering to decrypt Mail encrypted with GPG4Win 2.3.2.

Hi, VERY odd: My collegue has the exact same installation and environment (actually software deployment-based), she still is suffering to decrypt Mail encrypted with GPG4Win 2.3.2.

Virus scanner look for patterns seen in known viruses. However, legitimate software may have the same pattern as other software and thus also in viruses.

In T3367#106015, @RockyMM wrote:

Treat this as "Cannot Reproduce".

In T3419#105989, @hs wrote:

Just installed Version 3.0.1. From a first glimpse, it seems to work more stable in Outlook context.
But decrypting older plain text messages still fails.

Hi, also installed 3.0.1. For me decrypting older plain text messages now works!

Another log is not needed, as I located the issue. If you can try building GnuPG from Git repo (it's 2.2 branch now), it helps us a lot.