Page MenuHome GnuPG

Kleopatra: Encoding errors in signature verification audit log (timestamps)
Open, LowPublic

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

Event Timeline

timegrid created this object with edit policy "Contributor (Project)".

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…

my win10 vm was also installed with german language

werner edited projects, added gnupg26; removed kleopatra.
werner added a subscriber: werner.

I think we have another report on this in the tracker. The problem is indeed the ugly Windows time functions to print a string. Let me only remeber that untile a few years, Windows had the opinion that Germany is the the Westeuropäische Zeit, i.e. Portugal or the UK.

werner renamed this task from Kleopatra: Encoding errors in signature verification audit log to Kleopatra: Encoding errors in signature verification audit log (timestamps).Fri, May 9, 9:26 AM