[Gpg4win-users-en] --export creating utf-16 LE?

Bernhard Reiter bernhard at intevation.de
Wed Apr 3 09:17:28 CEST 2024

Hi Chris,

Am Dienstag 02 April 2024 12:49:57 schrieb Chris Jacobs:
> Using Gpg4win-4.3.1 on command line Windows 11

> PS C:\Users\chris> gpg -a --export test > test
> PS C:\Users\chris> gpg --import test
> gpg: [don't know]: partial length invalid for packet type 63
> gpg: read_block: read error: Ongeldig pakket
> gpg: import from 'test' failed: Ongeldige sleutelring
> gpg: Total number processed: 0

> Looking for the cause I found that gpg --export creates an utf-16 LE
> file and gpg --import expects ascii or utf-8 without bom but not utf-16 LE

thanks for reporting the problem!

I've did some initial testing on Windows 10 and could not reproduce so far.
So maybe this is a Windows 11 only problem, will do a test on such a system 

> The same test file imports good in Kleopatra.


https://intevation.de/~bernhard   +49 541 33 508 3-3
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer: Frank Koormann, Bernhard Reiter
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.wald.intevation.org/pipermail/gpg4win-users-en/attachments/20240403/b765eedc/attachment.sig>

More information about the Gpg4win-users-en mailing list