Bug 554718 – app-crypt/pinentry-0.9.5: Possible regression for symmetric encryption

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Kristian Fiskerstrand (RETIRED) 2015-07-13 09:10:15 UTC]

A user reported the following error from gnupg (2.1.6):

$ gpg -dvvv text/accts.txt.asc
gpg: using character set 'utf-8'
gpg: armor: BEGIN PGP MESSAGE
gpg: armor header: Version: GnuPG v2
# off=0 ctb=8c tag=3 hlen=2 plen=13
:symkey enc packet: version 4, cipher 3, s2k 3, hash 2
	salt C7F948F2BB5C7DA9, count 19922944 (227)
gpg: CAST5 encrypted data
gpg: problem with the agent: End of file
# off=15 ctb=c9 tag=9 hlen=2 plen=0 partial new-ctb
:encrypted data packet:
	length: unknown
gpg: encrypted with 1 passphrase
gpg: decryption failed: No secret key

Increasing debug verbosity for gpg-agent shows
2015-07-13 01:26:13 gpg-agent[32623] listening on socket '/home/<user>/.gnupg/S.gpg-agent'
2015-07-13 01:26:13 gpg-agent[32624] gpg-agent (GnuPG) 2.1.6 started
2015-07-13 01:26:14 gpg-agent[32624] handler 0x7f9f7ad22700 for fd 5 started
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 -> OK Pleased to meet you, process 32621
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 <- RESET
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 -> OK
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 <- OPTION ttyname=/dev/pts/5
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 -> OK
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 <- OPTION ttytype=screen-it
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 -> OK
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 <- OPTION display=:0
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 -> OK
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 <- OPTION putenv=XMODIFIERS=@im=ibus
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 -> OK
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 <- OPTION putenv=GTK_IM_MODULE=ibus
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 -> OK
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 <- OPTION putenv=QT_IM_MODULE=ibus
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 -> OK
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 <- OPTION lc-ctype=en_US.UTF-8
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 -> OK
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 <- OPTION lc-messages=en_US.UTF-8
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 -> OK
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 <- OPTION allow-pinentry-notify
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 -> OK
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 <- OPTION agent-awareness=2.1.0
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 -> OK
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 <- AGENT_ID
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 -> ERR 67109139 Unknown IPC command <GPG Agent>
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 <- GETINFO cmd_has_option GET_PASSPHRASE repeat
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 -> OK
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 <- GET_PASSPHRASE --data --repeat=0 -- SC7F948F2BB5C7DA9 X X Enter+passphrase%0A
2015-07-13 01:26:14 gpg-agent[32624] DBG: agent_get_cache 'SC7F948F2BB5C7DA9' (mode 3) ...
2015-07-13 01:26:14 gpg-agent[32624] DBG: ... miss
2015-07-13 01:26:14 gpg-agent[32624] starting a new PIN Entry
2015-07-13 01:26:14 gpg-agent[32624] DBG: connection to PIN entry established
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 -> INQUIRE PINENTRY_LAUNCHED 32626
2015-07-13 01:26:14 gpg-agent[32624] DBG: chan_5 <- END
2015-07-13 01:26:17 gpg-agent[32624] DBG: error calling pinentry: End of file <GPG Agent>
2015-07-13 01:26:17 gpg-agent[32624] command 'GET_PASSPHRASE' failed: End of file <Pinentry>
2015-07-13 01:26:17 gpg-agent[32624] DBG: chan_5 -> ERR 83902463 End of file <Pinentry>
2015-07-13 01:26:17 gpg-agent[32624] DBG: chan_5 <- [eof]
2015-07-13 01:26:17 gpg-agent[32624] handler 0x7f9f7ad22700 for fd 5 terminated

Downgrading to 0.9.4-r1 cause issue to not be reproduced. 
Using pinentry-curses by unsetting DISPLAY and setting GPG_TTY=$(tty) is NOT affected. 
This DOES affect the gtk variant.

Reproducible: Always

[Comment 1 Pacho Ramos 2015-07-23 15:05:43 UTC]

Any news about this? Is upstream aware of the issue? I couldn't find any patch or fix for other distributions like Fedora using this version, and I am unsure about how to help to get this solved sooner (specially as this is the only blocker for Gnome 3.16 going to stable :/)

Thanks

[Comment 2 Pacho Ramos 2015-08-03 10:56:02 UTC]

Also... is this also affecting to pinentry+gnupg-2.0.x (that is the combination that will hit stable users) ?

[Comment 3 Pacho Ramos 2015-08-10 11:41:41 UTC]

Any updates on this? This is the only blocker for Gnome 3.16 stabilization

Thanks

[Comment 4 Kristian Fiskerstrand (RETIRED) 2015-09-05 13:57:43 UTC]

(In reply to Pacho Ramos from comment #3)
> Any updates on this? This is the only blocker for Gnome 3.16 stabilization
> 
> Thanks

Symmetric encryption isn't the most used case of gnupg, so you can likely proceed with stabilization despite of this bug.

[Comment 5 Kristian Fiskerstrand (RETIRED) 2015-09-05 14:14:22 UTC]

(In reply to Kristian Fiskerstrand from comment #4)
> (In reply to Pacho Ramos from comment #3)
> > Any updates on this? This is the only blocker for Gnome 3.16 stabilization
> > 
> > Thanks
> 
> Symmetric encryption isn't the most used case of gnupg, so you can likely
> proceed with stabilization despite of this bug.

Just in case, added libassuan 2.2.1 to the stabilization queue in bug 552614, it is likely the reason I'm unable to properly reproduce this.

[Comment 6 Kristian Fiskerstrand (RETIRED) 2015-09-23 19:46:21 UTC]

We believe this issue is fixed in the current version. If the issue persists please re-open this bug.