Got a new OL 2013 test setup where this was finally reproducible for me.

I misunderstood your original report.

I updated the software to its latest version "gpg4win v3.1.1" and i'm still facing this issue.

Indeed. Thanks for the reminder.
There is some code currently in there already but its not yet fully implemented. Needs to be finished.

In the current gpg4win-3.1.3 beta 20 this is enabled again. It can be disabled in the options with "Disable non-blocking encrypt / sign"

I made it optional for now with default on. So that if it crashes it can be disabled. We need to see if the crash is a general problem or a special problem of that one tester.

This was fixed with kleo rev 289efa360f6b15a3389ea2f2efede352711e7d7e

I can't reproduce this. When I make Dirmngr offline I correctly get a No CRL known error. So it must be something different.

Yay. Got it.

Tester reports that this works now.

I got feedback from the user that had the problem. It's fixed with 2.2.9 which contains your commit afaik.

Dear Andre , all , T4020 does not even well-define the symptom and I
do not agree T4020 is a duplicate of T4079 . I'd close T4020 in favor
of T4079 . Many thanks . Mirko

Hi Mirko,

This was a misunderstanding. Import is possible. The german translation of Kleopatra wrongly indicated an error because it translated "unknown certificates" as "ungültige Zertifikate".

Commit rEbd5bcd2dd19ef0b1c3d33a3a388b537ba08a4eb6

it is not due to windows but due to the use of NTBTLS. I have the same problem here... and found it: We call es_fflush to let ntbtls flush its internal buffers but libgpg-error's estream module does no propagate this explicit flush to the cookie functions of ntbtls. Thus ntbtls gets stuck most of the time. I am not sure when this regression happened but it is pretty obvious.

I have logging to a socket always enabled. That may explain why I don't see that error on Unix.

There were two things here:

Works for me now.

On another note. We might also want to reduce the clicks required when certifying a key. The "I have checked the fingerprint" checkbox is out of time. People will check it regardless and we can't force them to do it.

This was a very clear crash that is fixed now. Length was > 76 characters. This caused an improper realloc.

No problem. I am glad that it works.

Boh. I've retried today, and seems to work as expected:

@Breach I was analyzing T4056 and wondered where I had seen the error from there before. And I found it in your log.

Thank you for your prompt response and your suggestion for a workaround.

Got it. The reason was a broken translation. I've opened T4054 to fix in general that broken translations can cause crashes.

I can reproduce it with a german windows

Thank you for your detailed report!

Now we have this:

Do you have Tor or the Tor Browser running? Dirmngr will use them instead of a direct or proxy network connection. Di disable this behaviour put

no-use-tor

into dirmngr.conf. If that is not the case we need some more debug info. Put

log-file SOMEFILE
verbose
debug network,dns

into dirmngr.conf and post the log file (or send privately to wk@gnupg.org mentioning T4044 in the subject - no HTML please).