| Summary: | >=app-crypt/gnupg-2.0.13 w/ app-crypt/pinentry[curses] and keychain hangs | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Alex Alexander (RETIRED) <wired> |
| Component: | Current packages | Assignee: | Crypto team [DISABLED] <crypto+disabled> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | de_doener, hwoarang, pkdevel, tove |
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
Seems to work fine with gnupg-2.0.15 (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. FYI, I think keychain was fixed. bug 203871 is related. Please verify that this is fixed with the latest keychain-2.7.1 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. |
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.