🚀 go-pugleaf

In article <1993Jan7.115335.1216@cs.aukuni.ac.nz> pgut1@cs.aukuni.ac.nz (Peter Gutmann) writes:
>-----BEGIN PGP SIGNED MESSAGE-----
> 
>I have posted the PGP 2.1 sources to alt.sources - see the posting itself for
>more details (I assume everyone knows what PGP 2.1 is :-).
> 
>Peter.
> 
>-----BEGIN PGP SIGNATURE-----
>Version: 2.1
> 
>iQCVAgUBK0wZd/oRqumdmX1HAQH54wP+NxF1ydxSAnfq2Hu4SaaA+nPE5hUO5hlL
>m+sNxfNO21vF4F+PWbBnDPG54RkZt5yLXQFdrJUrqvO1mupbohvpS5idxjGifNxu
>ReRCrYxrTrjyZoF1NPnp1hoXfo+VF2UK1v98HfaA8E0hsloaQJJA/Q5RSiU5iNIG
>wjg5TF7GIX4=
>=bsVc
>-----END PGP SIGNATURE-----

Like about half of the signed postings I have seen, Peter's arrived here
corrupted (NULL lines converted to lines with a single space in them).
This causes the messages to fail the signature check (it doesn't even
strip the armor correctly) until manually massaged.

Is this a problem for anyone else?  If so, perhaps the next release of pgp
should consider automatically stripping trailing blanks on "+clearsig" type
signed msgs, and perhaps try to account for other "mailer" type anomalies.  
-- 
Rob Stampfli  rob@colnet.cmhnet.org      The neat thing about standards:
614-864-9377  HAM RADIO: kd8wk@n8jyv.oh  There are so many to choose from.