January 16, 2026 at 8:28 pm
I will try that, thank you very much for your time. Thanks to Phil as well.
You folks have a great long weekend!
The are no problems, only solutions. --John Lennon
January 16, 2026 at 10:52 pm
also make sure the encrypted file is being sent in BINARY mode.
January 18, 2026 at 12:16 pm
UTF-8-safe argument
--output Somefile.txt.gpg
--encrypt
--recipient Somewhere@Someplace.com
--utf8-strings
Somefile.txt
January 19, 2026 at 8:08 pm
Try turning on ASCII armor which turns the file into ASCII for compatibility. It's still encrypted, but is sent in a format that the receiver can deal with. I've had to do this in the past with some recipients.
Some explanation here https://unix.stackexchange.com/questions/623375/what-is-the-armored-option-for-in-gnupg
January 21, 2026 at 7:12 pm
We are sending the ". GPG" file. We are checking with the client; we believe the issue is on their end. They claim the files is 90% invalid characters. This process has been running for a while with different encryption, but they recently changed to GPG encryption.
Thank you all for your help! I always learn something from this site. Have a great week.
Dave
The are no problems, only solutions. --John Lennon
January 21, 2026 at 7:16 pm
Hi Ross,
I never heard of Ascii armor before. Thank you for the knowledge share!
Dave
The are no problems, only solutions. --John Lennon
Viewing 6 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply