age fails to decrypt files generated in Windows PowerShell about age HOT 5 CLOSED

It looks like there are a couple bytes before the # in key.txt? Can you do a hexdump of the file?

from age.

Looking at the hexdump, it seems to be creating 2 random characters at the start.

Heres a gist of the hex dump: https://gist.github.com/BlackHoleFox/5dbfb60ba8d5180f2cbac53446597e4f

And heres a picture of HxD for easy viewing:

from age.

Yeah, that's a BOM, and it looks like the text got also converted to UTF-16 (notice the zero bytes).

That's not something we can support on the parsing side for sure, the file is effectively corrupt. Are we supposed to put stdout in some special mode to prevent this? I know next to nothing about PowerShell.

from age.

So, replacing the > with | out-file -encoding ASCII on both the key and encrypted file generation fixes the corruption issue, but it still seems the line endings are causing trouble.

By default, I get Error initializing decryption: failed to read header: parsing age header: unexpected intro: "This is a file encrypted with age-tool.com, version 1\r\n" while decrypting.

When I change the line endings of the files, I get Error decrypting the input: chacha20poly1305: message authentication failed, which makes sense considering I modified the .age file to change the EOLs to LF

from age.

The armored format (-a) should make it viable to use redirection in PowerShell. For binary files, use -o and the input argument.

from age.