TAB at EOL (GPG and PGP interoperability)
vedaal@hush.com
vedaal@hush.com
Wed Jan 15 17:07:03 2003
>Message: 8
>From: Ingo =?iso-8859-1?q?Kl=F6cker?= <ingo.kloecker@epost.de>
>To: gnupg-users@gnupg.org
>Subject: Re: TAB at EOL (GPG and PGP interoperability)
>Date: Wed, 15 Jan 2003 02:01:02 +0100
..
>Huh?
>
>If I run
>
>> echo "1234 6789 1234 6789 1234 6789 1234 6789 1234 6789 1234 6789
>1234=20
>6789 1234 6789 1234 6789 1234 6789 1234 6789 1234 6789 1234 6789
>1234=20
>6789 1234 6789 1234 6789 1234 6789 1234 6789" | gpg --clearsign
>
>then this will result in a single (not wrapped) clearsigned line.
>How do=20
>you make gpg wrap lines?
..
you are right.
sorry :(
was using the front ends for gnupg to sign,
and both win pt and gpgshell wrap at position 64 by default
checking it in the command line with just the --clearsign command produced no wrapping.
but i still don't understand something:
if the plaintext line ends in a 'tab' and is clearsigned by gnupg,
the signature will be 'bad' if the 'tab' is deleted from the end of the line in the clearsigned text,
so is gnupg calculating the 'tab' in the hash, even if it is at the end of a line,
and if it is, then why not have both gnupg and pgp agree to calculate it in the same way?
tia,
vedaal
Concerned about your privacy? Follow this link to get
FREE encrypted email: https://www.hushmail.com/?l=2
Big $$$ to be made with the HushMail Affiliate Program:
https://www.hushmail.com/about.php?subloc=affiliate&l=427