Thanks. I applied all 4 patches to master and did one additional change to get --allow-old-cipher-algos straight.

Tested encryption (+ signature) via Kleopatra with a 3 GB file (random data) with:

• VSD 3.2.4: ~ 5:20
• VSD 3.3.0: ~ 4:25
• command line; ~4:25

I never tested the WSL stuff with gpg-agent but I use the standard OpenSSH based ssh server on Windows on a daily base. It is actually part of our release build chain. A recent problem I encountered was fixed in master with rG2469dc5aae and should be backported to 2.4. Might be related to your problem but I need to read your detailed bug report more closely.

Here's all of the above patches squashed into a single patch:

attached here is a series of 4 patches that reinforce that the last --compliance policy option (or equivalent option, like --rfc4880 or --gnupg) supercedes any earlier one.

sorry for the confusion in the initial report -- the policy compliance option is of course --compliance, and not --policy, and i just miswrote it in one line of the description above. I've corrected it now, and all the rest of the report is still as it was.

Ok, then this will not be included in the VSD versions until we switch away from gpg 2.2

That gpg seems to be some other or patched software than the one from gnupg:

21f7ad563d9b was not backported to gnupg 2.2, so this can't be done yet

The commit rC58c11aa8 is the improved version by k-ary exponentiation (while rC6dffd105e2e2 is 1-bit at a time) and using heap.

It's missing a check for the required gpg-2.2 version. I will add that

Closing as there are now 2 follow up tickets for the open issues I found.