Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 328683

Summary: [app-crypt/pinentry-0.8.0] pinentry-curses hangs up via ssh
Product: Gentoo Linux Reporter: Gabor Garami <gabor.garami>
Component: New packagesAssignee: Crypto team [DISABLED] <crypto+disabled>
Status: RESOLVED NEEDINFO    
Severity: normal    
Priority: High    
Version: 10.0   
Hardware: All   
OS: Linux   
URL: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568375
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: emerge --info output

Description Gabor Garami 2010-07-17 00:08:30 UTC
The pinentry hangs up when i tried use gpg via 'git tag' command.
I unset GPG_AGENT_INFO environment variable, but the problem is still here.

Steps to reproduce:
1. Log in to any computer via ssh
2. unset GPG_AGENT_INFO
3. try use any program what uses gpg like "git tag -s"
4. requesting passphrase will hang up and you cannot do anything except Ctrl-C

Pinentry puts info message (3x):

pinentry-curses: no LC_CTYPE known - assuming UTF-8

This bug makes gpg unusable via ssh.
Comment 1 Gabor Garami 2010-07-17 00:09:34 UTC
Created attachment 239111 [details]
emerge --info output
Comment 2 Gabor Garami 2010-07-17 00:11:06 UTC
Pinentry and gnupg compiled by these flags:

[ebuild   R   ] app-crypt/pinentry-0.8.0  USE="-caps -gtk -ncurses -qt4 -static" 0 kB
[ebuild   R   ] app-crypt/gnupg-2.0.15  USE="bzip2 nls -adns -caps -doc -ldap -openct -pcsc-lite (-selinux) -smartcard -static" 0 kB


* Info: problem independent from ncurses USE flag on pientry.
Comment 3 Gabor Garami 2010-07-17 00:40:13 UTC
Similar bug here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=568375
Comment 4 Fabian Groffen gentoo-dev 2012-01-02 19:14:13 UTC
You have to set GPG_TTY to the output of tty as mandated by the gpg docs, see http://www.gnupg.org/documentation/manuals/gnupg/Common-Problems.html
Comment 5 Alon Bar-Lev (RETIRED) gentoo-dev 2012-12-22 00:41:29 UTC
Please reopen if you have further information, regarding behaviour with comment#4 applied.