On Wed, Dec 28, 2016 at 03:02:30AM -0500, Jeff King wrote: > > Is it a bug in gpg (oddly, the kernel reports lots of entropy available, > > and generating the signatures themselves is quite fast)? Or is the new > > version doing something special in the import process that we need to > > work around or disable? > > Answering my own question (somewhat): this is bisectable in the gnupg > repository, and it turns out to be caused by their 4473db1ef (agent: > Kludge to mitigate blocking calls in Libgcrypt., 2016-11-11), which > introduces a 100ms sleep (yuck) that is presumably triggering way more > than it needs to. More details at: > > > https://git.gnupg.org/cgi-bin/gitweb.cgi?p=gnupg.git;a=commit;h=4473db1ef24031ff4e26c9a9de95dbe898ed2b97 > > So this does seem like a gpg bug.
I've submitted a bug report to gpg: https://bugs.gnupg.org/gnupg/issue2897 so we'll see what they say. -Peff
