Crashes with gpg-agent 2.1.18

Justus Winter justus at
Mon Jan 30 11:03:08 CET 2017

Werner Koch <wk at> writes:

> [ Unknown signature status ]
> On Wed, 25 Jan 2017 13:58, justus at said:
>> It was a double free.  Fixed in
> Can you please describe in a code comment how xtrystrdup relinquishes
> control to another thread.  That is not easy to see:

No.  Because I wasn't able to see why it would, even though I did trace
it to gcrypt, and I did saw that it may use the secmem facilities.  I
was, however, sufficiently sure that I found and fixed the problem, and
I did add verbose comments to both the code and the commit message.

> It would also be useful to check other parts of gpg-agent and scdaemon
> which do secure memory allocations and may be prone to the same
> problem.

That occured to me as well.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: </pipermail/attachments/20170130/108ff436/attachment.sig>

More information about the Gnupg-devel mailing list