Follow-up to Crashes with gpg-agent 2.1.18

[Daniel Kahn Gillmor]

On Mon 2017-04-10 16:10:20 +0000, Shah, Amul wrote:
>> From: Shah, Amul Sent: Wednesday, April 05, 2017 11:24 AM
>> Subject: Follow-up to Crashes with gpg-agent 2.1.18
>>
>> I think that this is a follow up to a thread from January (last email in thread
>> https://lists.gnupg.org/pipermail/gnupg-devel/2017-January/032516.html) because it
>> started with me seeing the message "Ohhhh jeeee: ... this is a bug
>> (sexp.c:1433:do_vsexp_sscan)" in the gpg-agent log. Now in trying to reproduce the
>> error, the gpg- agent hits a PKDECRYPT failure claiming that it cannot allocate
>> memory.
>>
>> I tried debugging the error down into libgcrypt, but could not see where things
>> could go wrong unless the memory manager is not npthread safe. Since I made no
>> progress, I'm sending this mail along with a test case similar to the one from the
>> previous thread.
>>
>> Note that we don't encounter this problem with older GnuPG versions, GnuPG 2.15
>> and earlier.
>>
>> Could someone take a look at this or give me some pointers on how I can help
>> myself?
>
> [amul:1] No hints or suggestions? I guess I'll file a bug report instead and downgrade my
> Software.

Could you try with the version in debian experimental (2.1.20)?  I
believe the "Ohhh jeeee" crash was fixed upstream by commit
e175152ef7515921635bf1e00383e812668d13fc

        --dkg