Interaction will be something like this:

Priority is high, because Gnuk Token requires this feature for testing its implementation.

I ran gpgconf --kill gpg-agent and then the suggested command for i in {1..10}; do gpg -v --no-tty --verbose -o - encrypted.gpg 2>mylog.$i > /dev/null & done. (I was already running with --verbose, does -v add something else?)

In the interests of completeness I also tried it on a much larger file (1GB) which was both signed and encrypted. I also set the decryption to show the session key just to confirm it was decrypting since the plaintext was being sent to /dev/null.

I am unable to replicate this on OS X 10.9 Mavericks.

Running with -v would really be helpful.

In T4111#118259, @JJworx wrote:

That may be true, my Outlook crashes more often. Especially when dealing
with incoming S/MIME-signed mails!

This was a regression from 59e8a7ee3bcd16275091c9535626e49fc2a6c4af where a performance improvement to cache an object caused this problem.

Ah wait, I just remembered T4142. Maybe that is related. I'll try to reproduce that one first.

Again one of these issues I can't reproduce :-/

That may be true, my Outlook crashes more often. Especially when dealing
with incoming S/MIME-signed mails!

You are right. I originally left it open because it was in a different language but the first report. But it's cleaner to close it as a duplicate, also.

T4129 is also a duplicate.

Maybe not on Linux but the environment is visible from other processes in the same way as the command line. So I don't see why we should add yet more clumsy passphrase workarounds to gpg. We already have PINENTRY_USER_DATA which can fulfill the same task.

Thanks for the report. This was already reported andf fixed. We are aiming for a new Gpg4win / GpgOL Bugfix release soon to address this and other regressions.

i note that my patch doesn't include an addition to the test suite, which it probably should, though i'm not fluent in gpgscm. if someone could update it to include a test, i'd appreciate that, and would probably learn from the commit. I imagine the test would do something like:

I tried to push commit 07c19981da0607dc442fadc4079b1d71fbef8f83 to branch dkg/passphrase-env on playfair, but i got this complaint:

I made a large file for testing, but it doesn't matter. There's an arbitrary parallel limit where gpg will crash.

This issue prevents a user from accessing any other window on their system while the pinentry prompt is up. This issue is different than T2145. This issue is explicitly about the system-wide nature of the modal. The other issue is about auto-typing from a password manager.

Please see my comment on T4152.

Please check again with a recent upstream release or report to Debian. The release from Debian is pretty old and has a couple of non-standard patches.

updated example sent.

I confirm I have the same problem but, unfortunately, the beta did not help.

The self test error message looks like it originates from https://github.com/KDE/kleopatra/blob/master/src/selftest/enginecheck.cpp