Cannot read age keys in CRLF files about rage HOT 3 CLOSED

Here's the key I used in plain text for testing. This happens for all keys I generate but passphrases work fine.

# created: 2020-02-11T09:28:21-05:00
# public key: age18e02scpzf4llwcat8avadmt069uwt3wlym22zcgjkgqupgj75vrsyc36g6
AGE-SECRET-KEY-1TPCFMHDWCMWPMMT2RJL78MRWL5UZEGFWX4XPYTQTST07RAW7PAXQF6HA2N

from rage.

I figured it out. It's because I piped the key into a file with powershell. Resulting in \r\n control sequences in that test.key file. If I use the -o test.key it outputs the file with just \n.

rage should probably trim these off when reading in keys.

from rage.

Thanks for the report! The age format itself is very precise about its canonicity, so the format parser will not accept CRLFs. The key files OTOH have no such requirement, so it makes sense to parse both LF and CRLF there.

from rage.