PGP Outlook Express Plug-In Decryption Misses Line-Ends ..

Users of the web site send HTML forms to a secure UNIX based server over HTTPS. The secure server translates the forms into emails and encrypts the emails using PGP before sending them (the emails) to a single PC running XP.

It works fine without the PGP encryption ..

The problem is that with the PGP (layer) enabled the decryption process on the XP machine seems to translate the line-end characters incorrectly. The result is that all input lines of data are appended to form a single output line. The single output line of data appears to contain vertical bars where the line-ends should have occurred.

This is the latest version of Desktop PgP (ie. 8.x) ...  ?

Thanks,

        ChrisColeman.  

   
Chris ColemanAsked:
Who is Participating?
 
chris_calabreseConnect With a Mentor Commented:
The Unix standard is to end all lines with a newline (\n), while Windows ends all lines with cariage-return newline (\r\n).

Unix automatically adds the cariage-return to emails, but can't reach inside the PGP attachment to add them.

So, the solution is to add the cariage-returns to the HTML file before sending it to PGP (most Unix systems have a program called unix2dos or ux2dos to do this easily).

On the other other hand, since this is HTML, which doesn't require line-breaks, what's the problem?
0
 
Chris ColemanAuthor Commented:
 Ok, I guess from your reply that  UNIX is adding a carraige return to the complete PGP message after encryption, rather than adding the carraige returns to each line of input before encryption.

  Your suggestion to add \r\n to each line of the form input may solve the problem, because the \r\n could then be encrypted and decrypted by the Outlook Plug-in ..

   
0
 
Chris ColemanAuthor Commented:
Unfortunately adding \r\n to the form fields would not work.

Although I now have a solution, using the decrypt command twice from the OE plugin. On the first decrypt the message is decrypted with UNIX line-ends. On the second decrypt the missing ascii 13 is added and the message flows correctly down the page ..

Thanks.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.