Page MenuHome GnuPG

Wrong char encoding Gnupg -> agent -> pinentry
Closed, ResolvedPublic

Description

When the locale is set to e.g. iso-8859-1, gpg 2.0 will send a string like "Sie
benötigen eine Passphrase" (de_DE) in this encoding to the agent which in turn
transmits it to pinentry. If the string contains utf-8 encoded information from
a key, pinentry will get confused.

Gpg 1.4 /always/ used utf-8 for all strings sent to the agent/pinentry, even if
the locale was set differently. GnuPG 2.0 should also follow this approach.

Event Timeline

albrecht.dress set External Link to http://lists.gnupg.org/pipermail/gnupg-devel/2006-November/023389.html.Nov 27 2006, 9:18 PM

Marcus: gpg features the options

--display
--ttyname
--ttytype
--lc-ctype
--lc-messages

Pass them to all gpg's with a version >= 1.3.0

werner assigned this task to marcus.

I checked this in:

2006-11-29 Marcus Brinkmann <marcus@g10code.de>

  • rungpg.c: Include <unistd.h>. (gpg_new): Support --display, --ttyname, --ttytype, --lc-ctype and --lc-messages. Fixes T734.
werner removed a project: Testing.