Bug 307531 – >=app-crypt/gnupg-2.0.13 w/ app-crypt/pinentry[curses] and keychain hangs

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Alex Alexander (RETIRED) 2010-03-02 20:56:19 UTC]

I'm trying to use pinentry-curses with gnupg (and keychain), but it seems that using any gnupg version greater than 2.0.12 results in pinentry hanging (and using 100% of one CPU core).

gnupg-2.0.{11,12} works fine - the curses password dialog is shown.

to reproduce, add 
pinentry-program /usr/bin/pinentry-curses
to your ~/.gnupg/gpg-agent.conf

kill or clear any running gpg-agent
and run keychain YOURKEY.

[Comment 1 Markos Chandras (RETIRED) 2010-05-29 17:45:47 UTC]

Seems to work fine with gnupg-2.0.15

[Comment 2 Philip Kovacs 2010-06-28 02:39:40 UTC]

(In reply to comment #1)
> Seems to work fine with gnupg-2.0.15
> 

I can confirm that it doesn't work here either on x86.  I upgraded to gnupg 2.0.15 and, once again, I get a CPU 100% hang on the call to pinentry-curses.  
Same thing happened on 2.0.14. 

gnupg-2.0.11 is the highest version I can use to avoid this problem.

[Comment 3 Jeremy Olexa (darkside) (RETIRED) 2010-07-06 15:18:17 UTC]

FYI, I think keychain was fixed. bug 203871 is related.

[Comment 4 Markos Chandras (RETIRED) 2010-07-06 21:07:40 UTC]

Please verify that this is fixed with the latest keychain-2.7.1

[Comment 5 Philip Kovacs 2010-07-07 20:44:34 UTC]

Yes, I unmasked both keychain-2.7.1 (was at 2.7.0) and gnupg-2.0.15 (was at 2.0.11) and the hang on pinentry-curses appears to be fixed here on x86.

Thanks much.