cduffy at mvista.com
Mon Jun 19 09:40:41 CEST 2000
On Mon, Jun 19, 2000 at 09:35:46AM -0500, Ted Cabeen wrote:
> In message <200006190600.IAA02149 at dwimc.xsoft.at>, Alexander Zangerl writes:
> >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
> >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.
> 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.
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.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 240 bytes
Desc: not available
Url : /pipermail/attachments/20000619/8428521e/attachment.bin
More information about the Gnupg-devel