Crashes with gpg-agent 2.1.17

[Daniel Kahn Gillmor]

On Mon 2017-01-23 09:04:53 -0500, Patrick Brunschwig wrote:
> I got quite frequent crashes with gpg-agent on Mac OS X, and thus
> started to investigate what happens.
 [...]
> gpg-agent[30807]: retrieving cache entry
> 'E0935FE2D7829F0CA7580D98F58ECD6EF0A9DE25' failed: Cannot allocate memory
> gpg-agent[30807]: DBG: agent_get_cache
> 'E0935FE2D7829F0CA7580D98F58ECD6EF0A9DE25' (mode 2) (stored cache key) ...
> gpg-agent[30807]: DBG: ... hit
> gpg-agent[30807]: retrieving cache entry
> 'E0935FE2D7829F0CA7580D98F58ECD6EF0A9DE25' failed: Cannot allocate memory
> gpg-agent[30807]: failed to unprotect the secret key: Cannot allocate memory
> gpg-agent[30807]: failed to read the secret key
> gpg-agent[30807]: command 'PKDECRYPT' failed: Cannot allocate memory
> gpg-agent[30807]: DBG: chan_19 -> ERR 67141718 Cannot allocate memory
> <GPG Agent>
> gpg-agent[30807]: DBG: chan_19 <- HAVEKEY
> 06799B633E043A7665BBE85BDD883A71166B80B7
> gpg-agent[30807]: DBG: chan_19 -> ERR 67108881 No secret key <GPG Agent>
> gpg-agent[30807]: DBG: rsa_decrypt  res: [out of core]
> gpg-agent[30807]: Ohhhh jeeee: ... this is a bug
> (sexp.c:1433:do_vsexp_sscan)
>
> Is this a bug, or is it a config/setup error on my side?

What version of libgcrypt are you building against?  aiui, 1.7.4 and
later include a pretty major overhaul of the secmem pool handling, which
affects gpg-agent's ability to handle larger (or multiple) keys
concurrently.  So if gnupg is built against newer versions of libgcrypt,
maybe that would fix your issue?

hth,

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