Parallel decrypts fail in 2.1.19

Justus Winter justus at
Mon Mar 27 13:10:26 CEST 2017

Michael Smith <michaels at> writes:

> Hash: SHA512
>> Libgcrypt has the fix for the secure memory.  Thus the above should not
>> happen unless you have set an ulimit.  Are you sure that the running
>> gpg-agent is up-to-date?
>>    gpg-connect-agent 'getinfo version' /bye
> $ gpg-connect-agent 'getinfo version' /bye
> D 2.1.19
> OK
> I am on a MacBook Pro and haven't changed any defaults related to
> ulimits, but I'll take a look.
>> We need to have a test case to replicate and valgrind the problem.
> How can I help further to create a test case?

Can you please check which version of libgcrypt the agent is linked to?
E.g. by using 'otool':

$ otool -L repos/gnupg/obj/agent/gpg-agent
        /Users/justus/local/lib/libgcrypt.20.dylib (compatibility version 22.0.0, current version 22.3.0)
        /Users/justus/local/lib/libgpg-error.0.dylib (compatibility version 21.0.0, current version 21.0.0)
        /Users/justus/local/lib/libassuan.0.dylib (compatibility version 8.0.0, current version 8.3.0)
        /Users/justus/pkg/lib/libnpth.0.dylib (compatibility version 1.0.0, current version 1.5.0)
        /Users/justus/pkg/lib/libiconv.2.dylib (compatibility version 8.0.0, current version 8.1.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 1238.0.0)

Are you building GnuPG yourself?

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

More information about the Gnupg-users mailing list