[Bug 337988] New: gnupg using pinentry-qt exclusively for passphrase entry
https://bugzilla.novell.com/show_bug.cgi?id=337988 Summary: gnupg using pinentry-qt exclusively for passphrase entry Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: hatchmt@gmail.com QAContact: qa@suse.de Found By: --- I noticed that when using the cryptography plugin for kopete, I was getting prompted by pinentry-qt upon receipt of each encrypted message, whereas in 10.2 kopete would cache my passphrase for me. Later, I noticed that when running gpg from the CLI in a windowed session, it used pinentry-qt for that as well. So as a test, I switched to tty1 and ran gpg. It failed with the following: --------------- matthew@imladris:~> gpg passwords.gpg You need a passphrase to unlock the secret key for user: "<censored for posting in the bug>" 4096-bit ELG key, ID <censored>, created 2005-04-05 (main key ID <censored>) can't connect to `/home/matthew/.gnupg/log-socket': No such file or directory can´t lock memory: Cannot allocate memory Warning: using insecure memory! gpg: cancelled by user gpg: encrypted with 4096-bit ELG key, ID <censored>, created 2005-04-05 "<censored for posting in the bug>" gpg: public key decryption failed: General error gpg: decryption failed: No secret key matthew@imladris:~> --------------- When running in an ssh session, it brings pinentry-ncurses up and decrypts successfully. If this is by design, it's not a good thing. I use runlevel 3 a lot, so gpg from tty1-6 is a necessity. More importantly, it is a major pain to have to enter my passphrase upon receipt of every single message I receive with the kopete-cryptography plugin. FYI, this is reproducible on my i686 laptop, my brother's identical laptop, and my desktop running x86_64, all on 10.3. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=337988
Matthew Hatch
https://bugzilla.novell.com/show_bug.cgi?id=337988
Mark Gordon
https://bugzilla.novell.com/show_bug.cgi?id=337988
User hatchmt@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=337988#c1
--- Comment #1 from Matthew Hatch
https://bugzilla.novell.com/show_bug.cgi?id=337988
User nadvornik@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=337988#c2
Vladimir Nadvornik
Is there a way to adapt gpg-agent to not call 'pinentry' for passphrase entry? Here I don't understand what you want to achieve. The gpg-agent calls pinentry just once and then it uses cached password. It works at least on my machine.
To the choice of gpg2: supporting two versions forever is impractical, so we decided to switch to gpg2 and work on fixing possible problems. -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=337988
User hatchmt@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=337988#c3
--- Comment #3 from Matthew Hatch
https://bugzilla.novell.com/show_bug.cgi?id=337988
User pcerny@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=337988#c4
Petr Cerny
https://bugzilla.novell.com/show_bug.cgi?id=337988
User hatchmt@gmail.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=337988#c5
Matthew Hatch
https://bugzilla.novell.com/show_bug.cgi?id=337988
User pcerny@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=337988#c6
Petr Cerny
https://bugzilla.novell.com/show_bug.cgi?id=337988
User nadvornik@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=337988#c7
Vladimir Nadvornik
https://bugzilla.novell.com/show_bug.cgi?id=337988
User mhatch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=337988#c8
Matthew Hatch
https://bugzilla.novell.com/show_bug.cgi?id=337988
User mhatch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=337988#c9
--- Comment #9 from Matthew Hatch
https://bugzilla.novell.com/show_bug.cgi?id=337988
Petr Uzel
https://bugzilla.novell.com/show_bug.cgi?id=337988
User puzel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=337988#c10
--- Comment #10 from Petr Uzel
https://bugzilla.novell.com/show_bug.cgi?id=337988
User mhatch@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=337988#c11
--- Comment #11 from Matthew Hatch
https://bugzilla.novell.com/show_bug.cgi?id=337988
User puzel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=337988#c12
--- Comment #12 from Petr Uzel
https://bugzilla.novell.com/show_bug.cgi?id=337988
User puzel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=337988#c13
--- Comment #13 from Petr Uzel
https://bugzilla.novell.com/show_bug.cgi?id=337988
Petr Uzel
https://bugzilla.novell.com/show_bug.cgi?id=337988
User puzel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=337988#c14
--- Comment #14 from Petr Uzel
https://bugzilla.novell.com/show_bug.cgi?id=337988
User puzel@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=337988#c15
Petr Uzel
participants (1)
-
bugzilla_noreply@novell.com