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.
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.
--
,_, | Michael Nottebrock | lofi@freebsd.org
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org
character correctly. After some testing it turns out that gpg, if used
without gpg-agent seems to encode passphrases differently than the agents do.
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.
--
,_, | Michael Nottebrock | lofi@freebsd.org
(/^ ^\) | FreeBSD - The Power to Serve | http://www.freebsd.org
\u/ | K Desktop Environment on FreeBSD | http://freebsd.kde.org