Key creation problem with 2.1.16

[Neal H. Walfield]

Since this issue is still unresolved, I've open an issue so that it
doesn't get lost:

  https://bugs.gnupg.org/gnupg/issue2911

Thanks for taking the time to report this!

:) Neal

On Wed, 30 Nov 2016 00:04:29 +0100,
Carola Grunwald wrote:
> 
> [1  <text/plain; us-ascii (7bit)>]
> Hi,
> 
> after key creation, which usually succeeds, gpg.exe sometimes returns
> error number 2, which looks like a bug.
> 
> | gpg: DBG: get_keygrip for public key
> | gpg: DBG: keygrip= C5 A4 75 9F 78 43 21 40 44 66 AC A9 47 12 E4 F8 B5 A8 8B 02
> | gpg: DBG: chan_0x00000094 -> RESET
> | gpg: DBG: chan_0x00000094 <- OK
> | gpg: DBG: chan_0x00000094 -> SIGKEY C5A4759F784321404466ACA94712E4F8B5A88B02
> | gpg: DBG: chan_0x00000094 <- OK
> | gpg: DBG: chan_0x00000094 -> SETKEYDESC Please+enter+the+passphrase+to+unlock+the+OpenPGP+secret+key:%0A%22Gpg+Test+<gpgtest at nym.mixmin.net>%22%0A2048-bit+RSA+key,+ID+C738D5E556AFC7CE,%0Acreated+2016-11-24.%0A
> | gpg: DBG: chan_0x00000094 <- OK
> | gpg: DBG: chan_0x00000094 -> SETHASH 8 F682A7CB5487904584DC35C490D25ADE02BB223877C39C0398C49077E54EE6E9
> | gpg: DBG: chan_0x00000094 <- OK
> | gpg: DBG: chan_0x00000094 -> PKSIGN -- 071F0B591589B1AE96E29326
> | gpg: DBG: chan_0x00000094 <- S INQUIRE_MAXLEN 255
> | gpg: DBG: chan_0x00000094 <- INQUIRE PASSPHRASE
> | [GNUPG:] USERID_HINT C738D5E556AFC7CE Gpg Test <gpgtest at nym.mixmin.net>
> | [GNUPG:] NEED_PASSPHRASE C738D5E556AFC7CE C738D5E556AFC7CE 1 0
> | [GNUPG:] INQUIRE_MAXLEN 100
> | gpg: Sorry, we are in batchmode - can't get input
> 
> vs.
> 
> | gpg: DBG: get_keygrip for public key
> | gpg: DBG: keygrip= A5 82 DC 7B 32 E2 1A 79 82 9F 57 F7 A9 1B 2F 96 15 FB 43 C2
> | gpg: DBG: chan_0x00000094 -> RESET
> | gpg: DBG: chan_0x00000094 <- OK
> | gpg: DBG: chan_0x00000094 -> SIGKEY A582DC7B32E21A79829F57F7A91B2F9615FB43C2
> | gpg: DBG: chan_0x00000094 <- OK
> | gpg: DBG: chan_0x00000094 -> SETKEYDESC Please+enter+the+passphrase+to+unlock+the+OpenPGP+secret+key:%0A%22Gpg+Test+<gpgtest at nym.mixmin.net>%22%0A2048-bit+RSA+key,+ID+682B479F1A75E8C3,%0Acreated+2016-11-24.%0A
> | gpg: DBG: chan_0x00000094 <- OK
> | gpg: DBG: chan_0x00000094 -> SETHASH 8 657C84AFB05669CA8CD7721FFD634C4226C601311453F9E5667B747F75894F38
> | gpg: DBG: chan_0x00000094 <- OK
> | gpg: DBG: chan_0x00000094 -> PKSIGN -- 744E5829E93B414D3221D01E
> | gpg: DBG: chan_00000094 <- [ 44 20 28 37 3a 73 69 67 2d 76 61 6c 28 33 3a 72 ...(273 byte(s) skipped) ]
> | gpg: DBG: chan_0x00000094 <- OK
> | gpg: DBG: build_packet() type=2
> | gpg: DBG: iobuf-7.0: close '?'
> | gpg: DBG: armor-filter: control: 4
> | gpg: DBG: armor-filter: control: 5
> | gpg: DBG: iobuf-6.1: close 'armor_filter'
> | gpg: DBG: armor-filter: control: 2
> | gpg: DBG: iobuf-6.0: close 'file_filter(fd)'
> | gpg: DBG: G:/mob/Mail/MyGnuPG/gpg/openpgp-revocs.d\81A7B5FA786C103986170348682B479F1A75E8C3.rev: close fd/handle 176
> | gpg: DBG: fd_cache_close (176) real
> | gpg: revocation certificate stored as 'G:/mob/Mail/MyGnuPG/gpg/openpgp-revocs.d\81A7B5FA786C103986170348682B479F1A75E8C3.rev'
> | [GNUPG:] KEY_CREATED P 81A7B5FA786C103986170348682B479F1A75E8C3
> | gpg: DBG: free_packet() type=6
> | gpg: DBG: free_packet() type=13
> | gpg: DBG: free_packet() type=2
> | gpg: DBG: iobuf-1.0: close '?'
> | gpg: DBG: [not enabled in the source] stop
> | gpg: random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
> |               outmix=0 getlvl1=0/0 getlvl2=0/0
> | gpg: secmem usage: 0/32768 bytes in 0 blocks
> 
> I attached .exe i/o data of erroneous (gpg_cmd_ko.log) and normal
> processing (gpg_cmd_ok.log) as well as the respective --gen-key file.
> 
> Kind regards
> 
> Caro
> [2 gpg_cmd_ko.log <application/octet-stream (base64)>]
> [3 gpg_cmd_ok.log <application/octet-stream (base64)>]
> [4 key_gen.cfg <application/octet-stream (base64)>]
> [5  <text/plain; us-ascii (7bit)>]
> _______________________________________________
> Gnupg-devel mailing list
> Gnupg-devel at gnupg.org
> http://lists.gnupg.org/mailman/listinfo/gnupg-devel