pgp/mime vs in-line pgp

[Atom 'Smasher']

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> The whitespace issues are *in principle* also possible to work
> around for inline PGP: strip whitespace at end of line, and you're
> mostly safe.
=========================

you can add (or delete) as much white-space as you want at the ends of
lines, and that should NOT affect clearsigned signature creation or
verification.

you can test this by running:
  $ date | gpg --clearsign > test-file

then edit "test-file" to add spaces at the end of lines within the signed
data.... then:
  $ gpg --verify < test-file

should still say the signature is good.


RFC 2440, 7.1. Dash-Escaped Text:
"Also, any trailing whitespace (spaces, and tabs, 0x09) at the end of any
line is ignored when the cleartext signature is calculated."


        ...atom

 _________________________________________
 PGP key - http://atom.smasher.org/pgp.txt
 3EBE 2810 30AE 601D 54B2 4A90 9C28 0BBF 3D7D 41E3
 -------------------------------------------------

	"I am a former Los Angeles Police narcotics detective.
	 I worked South Central Los Angeles. And I can tell
	 you, Director Deutch, emphatically and without
	 equivocation, that the Agency has dealt drugs in this
	 country for a long time."
		-- Mike Ruppert to DCI John Deutch, 15 Nov 1996
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)
Comment: What is this gibberish?  -  http://atom.smasher.org/links/#digital_signatures

iEYEARECAAYFAkB87ywACgkQnCgLvz19QeNbNgCeL5+rVhhaj6kysJrDmj8HExaD
qmoAoI5OL0YjZp30AQYdS3nsCPDnNegN
=iVtK
-----END PGP SIGNATURE-----