Parallel decrypts fail in 2.1.19

Michael Smith michaels at syapse.com
Mon Mar 27 15:02:45 CEST 2017


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

> Can you please check which version of libgcrypt the agent is linked to?

$ otool -L $(type -P gpg-agent)
/usr/local/bin/gpg-agent:
        /usr/local/opt/libgcrypt/lib/libgcrypt.20.dylib (compatibility
version 22.0.0, current version 22.6.0)
        /usr/local/opt/libgpg-error/lib/libgpg-error.0.dylib
(compatibility version 23.0.0, current version 23.0.0)
        /usr/local/opt/libassuan/lib/libassuan.0.dylib (compatibility
version 8.0.0, current version 8.3.0)
        /usr/local/opt/npth/lib/libnpth.0.dylib (compatibility version
1.0.0, current version 1.5.0)
        /usr/local/opt/gettext/lib/libintl.8.dylib (compatibility
version 10.0.0, current version 10.5.0)
        /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
(compatibility version 150.0.0, current version 1348.28.0)
        /usr/lib/libiconv.2.dylib (compatibility version 7.0.0,
current version 7.0.0)
        /usr/lib/libSystem.B.dylib (compatibility version 1.0.0,
current version 1238.0.0)

> Are you building GnuPG yourself?

I first encountered the problem with the Homebrew binpkg. I also
rebuilt libgcrypt and gnupg using brew install --build-from-source.
The behavior has been consistent.

On Mon, Mar 27, 2017 at 7:10 AM Justus Winter <justus at g10code.com> wrote:
>
> Michael Smith <michaels at syapse.com> writes:
>
> > -----BEGIN PGP SIGNED MESSAGE-----
> > 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
> 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?
>
> Justus
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEFENfcrF4GOcIc0u0oCVjgPWyEDgFAljZDWMACgkQoCVjgPWy
EDh3yA/+IPvavITIZUkQ1nYEUTy7FcaCgD7AhOavj38iLE7anqr83I0PhbO1roCt
nCbyMnQGhqXqRGPm3lyHbi3qCOgDS4OfMQfzeMXMH51HIs0uQVPlOj2BQ3bS5qrw
8IXOAlTA8ZnsB7HrM+bSMKm3/o8dqo24tU2YJAJHu4sDczmNb7wIZ7Yh4TnrJjMe
PMYiDHytlAjVvbuVsH+P1pmxLUnN6h7Udnsp8Gkq1KLu9e7Xqlit0fOGo3+yTRIK
sc7GXCfEt3OFdkFI5R6xt+++qFuMgGrupTV54MAEL+lNBr1UFrdUBWmANz91lP83
LHYRE0nHuextdnI0fD2dy4+S+ToaFSG2elom/CwonfFRds5FI9aExDGUE0MfzmJ6
AFcgduHRtn6UVfbVKKki2MIDEaVlweL33kaUaPACo5RIFt3vo7MnFCuMhe01/Oci
aApWrikrWIrBfU6GqUCvKxmRkdhWZxFLXxzzHtZ6D9LdvQD3+1fhtEgKwD0waNQm
7Pc3vxdektXbq6xtwK2N/ScvpRFhu57hMuO3GDPyi5NPnGapLC+eshPA2B+C2X22
qHWnilXuS0rp3nUdzB/2RgT20wvF8WDe8Edt3RQmh1CKmofeFCM32Kr0cFOPkl+R
wL8w5hCFaqu5fA9aKOukenAWYpvlBcig7UJU2woyfeN+10gGHnU=
=Z0rQ
-----END PGP SIGNATURE-----



More information about the Gnupg-users mailing list