Had an interesting challenge during the encryption process for one of my client.
Client was sending a few ASCII files that were encrypted by the process and was producing expected end result after decryption. Then some time later, client started sending files with Unicode character set and was not getting proper LF/CR after decrypting files.
After some troubleshooting, I found that our encryption process was using "-t" (textmode) and was causing unexpected results for files that had unicode character set such as for Chinese and Japanese characters.
The issue was resolved after removing "-t" from encryption syntax.
Following was default encryption process.
gpg --no-secmem-warning -r XXX1234 -e -a -t --yes -o 'outfile.pgp' 'infile.txt'
and finally it worked fine with following syntax.
gpg --no-secmem-warning -r XXX1234 -e -a --yes -o 'outfile.pgp' 'infile.txt'
