Jason Gunthorpe <jgg@ualberta.ca> writes:
> I have tracked this down, the trouble seems to not be the gpg command but
> the file I am signing! [see below]
Thanks. The reason was quite simple: PGP2 does not think that a tab
belongs to the set of white space characters. Yes, this is then easier
to implement because you can simply count spaces and strip them when
you read the end of the line. You can't do this if there is a miy of
tabs and spaces.
I applied a couple of patches to detect pgp2 generated clearsigs and
to emit such bogus clearsig if either all recipient keys are old v3
RSA keys or option --rfc1991 is used.
Will show up on the CVS in some minutes.
--
Werner Koch at guug.de www.gnupg.org keyid 621CC013
> I have tracked this down, the trouble seems to not be the gpg command but
> the file I am signing! [see below]
Thanks. The reason was quite simple: PGP2 does not think that a tab
belongs to the set of white space characters. Yes, this is then easier
to implement because you can simply count spaces and strip them when
you read the end of the line. You can't do this if there is a miy of
tabs and spaces.
I applied a couple of patches to detect pgp2 generated clearsigs and
to emit such bogus clearsig if either all recipient keys are old v3
RSA keys or option --rfc1991 is used.
Will show up on the CVS in some minutes.
--
Werner Koch at guug.de www.gnupg.org keyid 621CC013