Problems creating keys since upgrade to Libgcrypt 1.7.x

steve (GPGTools) steve at
Thu Aug 25 11:31:44 CEST 2016

Dear all,

sending this to gnupg-devel feel free to forward / copy to gcrypt-devel.

Since we've upgraded the libgcrypt distributed in MacGPG 2.0.30 to 1.7 from 1.6.5, we've received different user reports which state that sometimes creating their first key fails for them.
GnuPG simply aborts with error code 99 (cancelled)
We're calling gnupg with the following options:
--no-greeting --no-tty --with-colons --fixed-list-mode --utf8-strings --display-charset utf-8 --enable-special-filenames --yes --output - --status-fd 3 --batch --passphrase-fd 6 --gen-key --no-armor --no-textmode --no-emit-version -- -&5

We've managed to reproduce the problem consistently on one of our machines by following these steps:
- Remove .gnupg folder
- Create new key pair (using GPG Keychain on Mac)
First attempt fails, second works.

On a second computer we've only managed to reproduce the bug some of the time.

As mentioned before, reverting libgcrypt to 1.6.x solves the problem.

We were wondering if you Werner or others have any idea what changes from 1.6.5 (we have yet to try 1.6.6) to 1.7 might be related to the described bug. 1.7.0 and 1.7.3 have been tested with the same results.


steve and team
-------------- next part --------------
An HTML attachment was scrubbed...
URL: </pipermail/attachments/20160825/30383b14/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: </pipermail/attachments/20160825/30383b14/attachment.sig>

More information about the Gnupg-devel mailing list