^M characters are embedded at the end of every record.

Steve Butler sbutler@fchn.com
Wed Nov 6 23:11:01 2002

Try using the --armour flag on encryption.  That will make the file bigger.

You might also use a tool to change a DOS file to a UNIX file after it has
been decrypted.  

That is part of what FTP does when you send a file in ASCII mode from a
Windows type box (where line terminators are the <CR><LF> pair of
characters) to a Unix type box (where line terminators is a single <LF>
character).  The ^M character is really a <CR>.  FTP removes the <CR> that
immediately precedes an <LF> character.

Which is why an encrypted file (non-ASCII armoured) always needs to be
FTP'ed as binary.  Should a <CR><LF> sequence show up in the datastream (and
they do!), the ASCII mode will remove the <CR> leaving a corrupted file.

-----Original Message-----
From: Loo, Peter [mailto:Peter.Loo@bannerhealth.com]
Sent: Wednesday, November 06, 2002 1:24 PM
To: gnupg-users@gnupg.org
Subject: ^M characters are embedded at the end of every record.

Hi All,

I created a text file in Windows environment.  Then it is encrypted and
FTPed to a Unix server where the file is decrypted.  After decryption, I am
seeing ^M characters at the end of each record.  I have tried sending the
file in both ASCII and BINARY modes.  Both modes don't help.  However, if I
send the plain text file via FTP in ASCII mode, the file does not contain
and control characters.  Is there a way to decrypt the file into an output
file without ^M character or is there a way to encrypt the file without ^M?

Thanks in advance.


Gnupg-users mailing list

CONFIDENTIALITY NOTICE:  This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information.  Any unauthorized review, use, disclosure or distribution is prohibited.  If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.