New submission from Bernhard Herzog <bh@intevation.de>:
When exporting secret keys with kleopatra, non-ascii characters in the text
displayed by pinentry is handled incorrectly. When exporting a secret key, a
pinentry window comes up two times, once to unlock the secret key, and once to
protect the pkcs12.
When using pinentry-gtk, non-ascii characters are shown incorrectly in the first
message, but correctly in the second. When using pinetry-qt it's the other way
round.
my guess is that the lc-ctype is not communicated to the pinentry, and that the
second message is in the locale's ctype and not in utf8.
This looks mostly like a backend bug to me.
----------
assignedto: werner
messages: 779
nosy: bh, werner
status: unread
title: non-ascii wrong in pkcs12 export
topic: certmanager
______________________________________________________
Aegypten issue tracker <aegypten-issues@intevation.de>
<https://intevation.de/roundup/aegypten/issue168>
______________________________________________________
When exporting secret keys with kleopatra, non-ascii characters in the text
displayed by pinentry is handled incorrectly. When exporting a secret key, a
pinentry window comes up two times, once to unlock the secret key, and once to
protect the pkcs12.
When using pinentry-gtk, non-ascii characters are shown incorrectly in the first
message, but correctly in the second. When using pinetry-qt it's the other way
round.
my guess is that the lc-ctype is not communicated to the pinentry, and that the
second message is in the locale's ctype and not in utf8.
This looks mostly like a backend bug to me.
----------
assignedto: werner
messages: 779
nosy: bh, werner
status: unread
title: non-ascii wrong in pkcs12 export
topic: certmanager
______________________________________________________
Aegypten issue tracker <aegypten-issues@intevation.de>
<https://intevation.de/roundup/aegypten/issue168>
______________________________________________________