Parallel decrypts fail in 2.1.19

Michael Smith michaels at syapse.com
Thu Mar 23 22:26:52 CET 2017


-----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?

Thanks,
Michael

On Thu, Mar 23, 2017 at 1:29 PM, Werner Koch <wk at gnupg.org> wrote:
> On Thu, 23 Mar 2017 02:32, michaels at syapse.com said:
>
>> 2017-03-22 21:25:14 gpg-agent[3624] DBG: rsa_decrypt  res: [out of core]
>> 2017-03-22 21:25:14 gpg-agent[3624] Ohhhh jeeee: ... this is a bug
>> (sexp.c:1433:do_vsexp_sscan)
>
> The bug diagnostic is a side-effect of the out of core error.  I'll fix
> that for libgcrypt 1.8 but it is not a problem.
>
>> $ gpg --version
>> gpg (GnuPG) 2.1.19
>> libgcrypt 1.7.6
>
> 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
>
> shows this.  However, gpg did not show a warning so I expect this is
> all fine.
>
> We need to have a test case to replicate and valgrind the problem.
>
>
> Salam-Shalom,
>
>    Werner
>
> --
> Die Gedanken sind frei.  Ausnahmen regelt ein Bundesgesetz.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEFENfcrF4GOcIc0u0oCVjgPWyEDgFAljUPUcACgkQoCVjgPWy
EDgEpA//R6qjcX7cSu9oRgSSGqRsROeNU7qeNie/JC2gKbUG1tXvnpYTjnoKKxXH
nElnd0laLTgWFZB4f2a8XtmFA0Ofca/rmmgQ/uVfCAdxcpsmFmRnQMBVnteXIxzy
SHhR2+980JU6gSG/gfdJ1ezVYDvU3MlM0MVb/EzMsjeA6MeKCGpg5Anc21ymO4mo
iWjp0sBC8f3aOn9zJBSmqmejqPKcyhlYl6khM3w5Q6pYFCF1B2b3VtO2F+qxrSWS
cVePVz+HVREkvPeOfi5tbN6ENaWWLQUhm5aGZl/Jsg+GJ6mD1TyOv3ZZSqVvZgjh
m11xPAFyHvvphk2ILa1X0TmTnSXUD9JZnX5RhLcUW4x/JICCidghjb+RKXyb7bNK
naaGjI47kCqBP38HZZpydOdBlnsQ60M/14/s9QUi2lkrhYtkrSzoB7vKLRoKIMwc
KJlzl29TKXbGbH8p3hikpFfJuAggUIZekALTlLcQfAXCBlLxwRf0zKehke8T8xIJ
Cc/j7V9parH3x7R4jbkd5uPyoGjpD2ivJJ3pnBTgbaH0CuWbhErDiFN9jIfUaqJc
BIC5A3qRDcbVJodzuQE1sVqeAstJaWv0E+FBrTGRrd6b7xppiRK5kpRGEb2VrhD3
I8JaYS1EesqCHLN9rRKWVT1eYJA7Pfg738qAi4KoYdPGxADc4Mw=
=kTy8
-----END PGP SIGNATURE-----



More information about the Gnupg-users mailing list