Re: Incompatible passphrase encoding in gpg/gpg-agent?
Bernhard Reiter <[email protected]> Tue, 12 Apr 2005 20:38:49 +0200
| Newsgroups | gmane.comp.encryption.gpg.gpa.devel |
|---|---|
| Message-ID | <[email protected]> |
On Sun, Apr 10, 2005 at 01:51:05PM +0200, Michael Nottebrock wrote: > Bernhard Reiter sagte: > > 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. > I've tested this with gpg and the pinentries running in the same > x11-session with the same locale and encoding (de_DE.ISO8859-15, I believe > that charset is called @euro in glibc-land). It should be easily reproducable. Werner: Where would you like the bug report for this issue? _______________________________________________ Gpa-dev mailing list [email protected] http://lists.gnupg.org/mailman/listinfo/gpa-dev
signature.asc
(application/pgp-signature, 189 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQBCXBW5h9ag3dpKERYRAt4mAJwK+okInI2wxCcx4xlTV3zYfXgc8gCcDAme M/WfpJocIfRVPod/18g0+qI= =lpAA -----END PGP SIGNATURE-----