Hi,

I'm Having problem with gpg decrypted file. I can successfully encrypt file in Linux and try to decrypt in in a windows workstation. Here is the thing when i try to open the decrypt file in notepad the "next line (enter)" was change to a "box character" and the messages was read as a one linner, i already tried openning it using Word and it looks fine, but the problem is i need to open it in notepad because "the process should be like that". I also tried signing the encrypt file logically the file was not altered since the sign is the same but the box character are still appeared, also tried to tar first the file before encryption again same thing happen.Is there a way so the box character wont change the "nextline"? Hope you can help me in this one

I'm very much a Linux Newbie, but I suspect that the "box" characters you are seeing displayed on the screen are characters that your version of Window$ will not allow to be displayed, or is unable to display. They could be characters in the extended ASCII character set (such as e-acute - é), or perhaps the matter is more serious and the file is somehow being corrupted. Have you tried to compare the original unencrypted text with the decrypted text? Remember that Micro$oft Internet Explorer has a mind of its own - I ran a spelling check on this posting, and it wanted to change Newbie and é (though left Micro$oft alone.....)

Well, Linux (& Unix) use \n as a newline char, MSDOS (WIN) uses \r\n. It may be that Word can cope, but Notepad can't.
I can't test that as I don't have MS at home.
You can try using /usr/bin/unix2dos to convert before encryption.

thanks but i already found a solution in this matter, turns out gpg has the option were you can specify that the file is a textfile i include the -t or -textmode in the gpg command just like below

gpg --output /root/quia_praktis/EM11081118.txt.gpg -cts EM11081118.txt


then after the i transfered the gpg file from linux to windows and decrypt it, i got the same data without any alteration. In the mannual for gpg it explains that -t or -textmode "Treat input files as text and store them in the OpenPGP canonical text form with standard "CRLF" line endings. This also sets the necessary flags to inform the recipient that the encrypted or signed data is text and may need its line endings converted back to whatever the local system uses. This option is use-ful when communicating between two platforms that have different line ending conventions (UNIX-like to Mac, Mac to Windows, etc)."


thanks=D...