Signing problems...
Alexander Zangerl
a.zangerl@xsoft.at
Mon, 19 Jun 2000 16:50:59 +0200
This is a multi-part message in MIME format.
It has been signed conforming to RFC2015.
You'll need PGP or GPG to check the signature.
------------=_961426286-1241-14
Content-Type: text/plain; charset=US-ASCII
On Mon, 19 Jun 2000 09:35:46 CDT, Ted Cabeen writes:
>You're right. The question is what do we do with this bug?
fix it, of course ;-)
but serious: i'll dig into the details of this problem during the
next few days.
>Is there a flag
>in the PGP signature spec that informs the client that this mode is on?
as i parsed rfc2440, yes.
>What
>do the other clients do?
as far as i've tried & tested, they do like they should: strip trailing
whitespace when generating signatures and when verifying them.
gpg currently does the first thing ok, but fails at the second task.
so, this very mail which does not verify ok by gpg (because of "-- " in
front of my signature) should check ok if tested with pgp.
alternatively you can make the sig match the data if you manually delete
all trailing whitespaces.
> 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.
no, the necessary info what transformations to perform before computing
the signature are transported.
regards
az
--
++ Dipl.-Ing. Alexander Zangerl Xsoft GmbH. ++
++ a.zangerl@xsoft.at http://www.xsoft.at/ ++
++ phone +43 1 7963636 - 28 fax +43 1 7963636 - 18 ++
------------=_961426286-1241-14
Content-Type: application/pgp-signature; name="signature.ng"
Content-Disposition: inline; filename="signature.ng"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjlOM24ACgkQ1FnlLzB2kCRz4gCgoprFZ/sR26hCRv+k/RQExRdF
YUYAoKcF/KuRFoAWhK0d4PHhLpCYIy9c
=aAUE
-----END PGP SIGNATURE-----
------------=_961426286-1241-14--