Page MenuHome GnuPG
Create Task
Maniphest T4871

gpg lock invalid key size due to not running UTF-8 encoding on Windows
Closed, InvalidPublic
Actions

Description

I was having issues with gpg and lock files.
Until I realized my issue was related to my windows 10 install not using chcp 65001 ?

Windows 10 2004 (insiders)
gpg (GnuPG) 2.2.19
libgcrypt 1.8.5

Event Timeline

Jetersen created this task.Mar 9 2020, 8:55 PM
Jetersen created this object in space S1 Public.
Jetersen added projects: gpg4win, gnupg.Mar 9 2020, 10:42 PM
• aheinecke added a subscriber: • aheinecke.Mar 10 2020, 10:16 AM

Hi,

apologies but I do not understand this issue. Please clarify. Were you having issues with "log" files or "lock" files?
What was your issue?

When opening log files your editor should handle encoding. Ok if you use notepad you might have a problem with different encodings.

Thanks,
Andre

Jetersen added a comment.EditedMar 10 2020, 11:27 AM

At no point did I mention log files ? So not sure where that is coming from.

Specifically I had issues when trying to sign a commit with gpg it would attempt to sign and in the process lock and fail afterwards with "invalid size of lockfile .gnupg/pubring.kbx.lock

dkg added a subscriber: dkg.Mar 10 2020, 4:23 PM

Hi @Jetersen!

"log" and "lock" are easy typo/confusions to make, @aheinecke was just trying to understand your report better, since there wasn't much information in it.

Can you outline the specific steps you took, and the full error messages?

a transcript of a cmd.exe session might be useful, for example.

Also, i have no idea what chcp 65001 is. maybe provide a pointer or a link, if you think it's relevant.

Jetersen closed this task as Invalid.Mar 10 2020, 4:51 PM
Jetersen removed subscribers: dkg, • aheinecke.
Jetersen removed a subscriber: Jetersen.