Space-padded lines in crypt-text
Dave Hill
dhill@wgate.com
Wed Mar 20 18:53:02 2002
This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
------_=_NextPart_001_01C1D037.56A2C0D0
Content-Type: text/plain;
charset="iso-8859-1"
Hi all. I've run into a problem running GnuPG on text copied out of an
email in Eudora or Netscape. With the right combination of circumstances,
the GPG text ends up padded with a space at the end of each line (ie
space-cr-lf or space-lf on every line). The spaces in the crypt-text block
itself don't cause GPG a problem, but the space at the end of the -----BEGIN
PGP MESSAGE----- line causes GnuPG not to recognize the block as valid
crypt-text. I was wondering:
1) Why does the space in the BEGIN line cause a problem, but not the spaces
in the crypt-text block?
2) If it makes sense, could someone in the group implement a fix that
wouldn't break other stuff in the process?
Thanks for any input you can provide,
Dave Hill
WorldGate Communications, Inc.
------_=_NextPart_001_01C1D037.56A2C0D0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
5.5.2653.12">
<TITLE>Space-padded lines in crypt-text</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=3D2>Hi all. I've run into a problem running GnuPG =
on text copied out of an email in Eudora or Netscape. With the =
right combination of circumstances, the GPG text ends up padded with a =
space at the end of each line (ie space-cr-lf or space-lf on every =
line). The spaces in the crypt-text block itself don't cause GPG =
a problem, but the space at the end of the -----BEGIN PGP MESSAGE----- =
line causes GnuPG not to recognize the block as valid crypt-text. =
I was wondering:</FONT></P>
<P><FONT SIZE=3D2>1) Why does the space in the BEGIN line cause a =
problem, but not the spaces in the crypt-text block?</FONT>
</P>
<P><FONT SIZE=3D2>2) If it makes sense, could someone in the =
group implement a fix that wouldn't break other stuff in the =
process?</FONT>
</P>
<P><FONT SIZE=3D2>Thanks for any input you can provide,</FONT>
</P>
<P><FONT SIZE=3D2>Dave Hill</FONT>
<BR><FONT SIZE=3D2>WorldGate Communications, Inc.</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C1D037.56A2C0D0--