Signing problems...
Charles Duffy
cduffy@mvista.com
Mon, 19 Jun 2000 08:40:41 -0700
--0OAP2g/MAC+5xKAE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Jun 19, 2000 at 09:35:46AM -0500, Ted Cabeen wrote:
> In message <200006190600.IAA02149@dwimc.xsoft.at>, Alexander Zangerl writ=
es:
> >On Fri, 16 Jun 2000 15:28:02 CDT, Ted Cabeen writes:
> >>I found the bug. With the above command line, GPG chokes on input
> >>lines that end in a space character. It will generate a
> >>signature, but that signature will not match the original text,
> >>with the trailing space.
> >
> >i've run into a similar problem in february, see
> ><URL:http://lists.gnupg.org/gnupg-devel-200002/msg00026.html>.
> >
> >personally i think your problem is the same as mine, i.e. that gpg
> >does strip trailing whitespace correctly when signing
> >but not when checking the signature.
>=20
> You're right. The question is what do we do with this bug? Is
> there a flag in the PGP signature spec that informs the client that
> this mode is on? What do the other clients do? I fear that even if
> GnuPG correctly generates the signature, other OpenPGP clients will
> not know that we were in this mode, and will have the same problems
> that gpg is currently having. =20
Well, we can try checking both ways when verifying if trailing
whitespace is found anywhere in the file, as at least a temporary fix.
As for other programs, if they meet the spec they'll strip whitespace;
If they don't, they're by definition not OpenPGP clients.
--0OAP2g/MAC+5xKAE
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE5Tj75r/O29KUQmJURAsStAJ940QWGEuIIKPxYqq9VZZoizScz8wCfT5V4
+1RDcECa/d002tEqJG2OFFg=
=SvaW
-----END PGP SIGNATURE-----
--0OAP2g/MAC+5xKAE--