Page MenuHome GnuPG
Create Task
Maniphest T7645

Kleopatra: Encoding errors in signature verification audit log
Open, Needs TriagePublic
Actions

Description

The encoding of the signature verification audit log seems broken:

@ikloecker wrote in https://dev.gnupg.org/T6869#200690

Apparently, gpg prints the time (zone) with a different encoding than its own texts (e.g. "EDDSA-Schlüssel"). I suspect that a POSIX function is used for printing the time and that one doesn't know that gpg wants to print everything with UTF-8 encoding. We wouldn't have this problem if gpg would use LANG=C. I'm wondering why gpgme doesn't call gpg with LANG=C to avoid any problems with non-ASCII characters.

Note: This screenshot from around Dec 8 2023 in T6869 doesn't have those errors:

Details

Version
gpg4win-5.0.0-beta167@win10

Related Objects

Event Timeline

timegrid created this task.Thu, May 8, 10:49 AM
timegrid created this object with edit policy "Contributor (Project)".
• ebo added a comment.EditedThu, May 8, 11:05 AM

Note that old screenshot was made with a version using a gpg from the 2.2 branch.
And on a Windows VM which was (I'm quite sure) installed in German from the start.
In case it matters…

timegrid mentioned this in T6869: Kleopatra: Improve verification results messages (esp. for invalid signature and multiple signatures).Thu, May 8, 11:08 AM
timegrid added a comment.Thu, May 8, 11:17 AM

my win10 vm was also installed with german language