https://bugzilla.novell.com/show_bug.cgi?id=364367 User puzel@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=364367#c11 --- Comment #11 from Petr Uzel <puzel@novell.com> 2008-07-08 07:25:11 MDT ---
However, the problem might not be gpg itself but its integration into the openSUSE 10.3 environment: since 10.3 gpg opens a new X-Window for entering the passphrase, even if initiated from a text console.
OpenSUSE 10.3 was the first release with gnupg 2.x which uses pinentry to get passphrase from the user (former gnupg version did not use any external utility at all and thus worked only with console).
I did not find how to run gpg entirely in console mode. Is there a switch to turn off opening a window for passphrase entering - to enable entering the passphrase on a text console?
There's a script /usr/bin/pinentry that tries to find out the correct binary to call - pinentry-qt/-qtk/-curses (this is not a simple task BTW). So if you want to enforce gpg to call pinentry-curses, you can adjust the script or directly replace it with the right binary. I'll do some more investigation but I'm pretty convinced that the bug is caused by already solved UTF-8 problems and that it would not happen again with newly created passphrases... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.