Re: Incompatible passphrase encoding in gpg/gpg-agent?

On Wed, Mar 30, 2005 at 05:35:27PM +0200, Michael Nottebrock wrote:
> I have recently received a bugreport about pinentry-qt not handling the "§" 
> character correctly. After some testing it turns out that gpg, if used 
> without gpg-agent seems to encode passphrases differently than the agents do.

That probably is a locale and encoding issue.
Of course the pinentries should use the current locale and if they
run on X11 they are influenced by those settings, too.

In order to debug this, you could try with several locales
and also try to see if xev and on the terminal, 
the same key symbols will be created.

> Testcase: Run gpg without agent active, use passwd to change a key passphrase 
> to "test§test". Save. Then run gpg-agent (any pinentry variant will do) and 
> try to change the passphrase again with gpg. Gpg won't accept the passphrase 
> string delivered by gpg-agent. Unset the GPG_AGENT_INFO env var and change 
> passphrase in gpg without agent - works.
> 
> This is with gpg from GnuPG 1.4.0, gpg-agent from GnuPG 1.9.14 and pinentry 
> 0.7.1.

_______________________________________________
Gpa-dev mailing list
[email protected]
http://lists.gnupg.org/mailman/listinfo/gpa-dev

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD4DBQBCTSQAh9ag3dpKERYRApCMAJ9CdAei2gVQ7+3G3QKmgv1dxxCkBACWLfbB
/9xDv5Hj8tc2D3ZwczKS5Q==
=enX7
-----END PGP SIGNATURE-----