Red Hat Bugzilla – Bug 704495
gpg-agent does not support utf-8
Last modified: 2015-07-13 00:14:44 EDT
Created attachment 498757 [details]
garbled output from gpg when asking for password
Description of problem:
gnupg2 requires usage of agent to retrieve key passphrase. Console version of this agent doesn't seem to support UTF-8 properly - see the attached screenshot.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
Use gpg on a key which contains non-ascii characters in its name.
The output is garbled
The output is clean.
Detected on ScientificLinux 6 but I guess this is also a case on RHEL.
I do not think this is a bug in the gnupg2. I suppose there is non-utf8 locale set in the gnupg2 agent environment.
Can you call 'unset GPG_AGENT_INFO' before runing the gpg2 command and test it again?
I don't think this is a reason:
triss:~> set | grep GPG
But to make sure I am not missing anything, I tried:
triss:~> unset GPG_AGENT_INFO
triss:~> gpg -d ~/pliki/txt/dane.txt.asc
with exactly the same problem as in the screenshot.
And locale for completness:
Now, the problem looks very similar to fault in finger, which also garbled UTF-8 output, this was caused by outputting a string byte by byte with putc instead pushing whole string at once to terminal. Maybe this is the case?
What terminal do you use?
I can reproduce this on:
- local text console (linux)
- remote linux console (text console + ssh connection)
- local konsole (kde konsole)
- remote konsole (kde konsole + ssh)
konsole identifies itself as xterm (TERM=xterm)
I take back local konsole part - in this case dialog box is displayed and my name is displayed correctly.
The terminal output is handled by pinentry.
Created attachment 499280 [details]
pinentry-curses garbled output
I tried the following in pinentry-curses:
OK Your orders please
which resulted in the attached above screen. This seems to confirm that a problem is in pinentry.
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
The bug can be reproduced in also in RHEL 6. Thank you for the bugreport.
For the record, upstream fixed this. Have yet to look at possible backporting.
*** Bug 1191639 has been marked as a duplicate of this bug. ***
dist-git commits related to build pinentry-0.7.6-8.el6:
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.