New submission from Bernhard Herzog <bh@intevation.de>:
The protect tool seems to have a character encoding problem.
When exporting a secret key for example, a pinentry come up where non-ascii
characters in the subject dn are not shown correctly. Tested with pinentry-qt
and pinentry-gtk. AFAICT, characters with the 8th bit set are converted to
bytes with all bits set.
When importing a pkcs12 file, I get a German message where the non-ascii
characters are wrong in the same way (\xFF bytes instead of umlauts).
----------
assignedto: werner
messages: 437
nosy: bh, werner
priority: bug
status: unread
title: protect-tool: utf8 problem
topic: gpgsm
______________________________________________________
Aegypten issue tracker <aegypten-issues@intevation.de>
<https://intevation.de/roundup/aegypten/issue103>
______________________________________________________
The protect tool seems to have a character encoding problem.
When exporting a secret key for example, a pinentry come up where non-ascii
characters in the subject dn are not shown correctly. Tested with pinentry-qt
and pinentry-gtk. AFAICT, characters with the 8th bit set are converted to
bytes with all bits set.
When importing a pkcs12 file, I get a German message where the non-ascii
characters are wrong in the same way (\xFF bytes instead of umlauts).
----------
assignedto: werner
messages: 437
nosy: bh, werner
priority: bug
status: unread
title: protect-tool: utf8 problem
topic: gpgsm
______________________________________________________
Aegypten issue tracker <aegypten-issues@intevation.de>
<https://intevation.de/roundup/aegypten/issue103>
______________________________________________________