-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Friday 14 March 2003 12:12 pm, Patrick Shanahan wrote:
xxxx pgpgp unsigned xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
* Tom Emerson
[03-14-03 14:36]: ... snip ...
[and more sniping]
- -- Yet another Blog: http://osnut.homelinux.net -----BEGIN PGP SIGNATURE-----
notice the line above 'Yet another Blog:', another ?broken? sig-indicator. Is gpg/pgp doing it or kmail or gpg/pgp/kmail?
very likely as I review this -- some behind the scenes stuff is going on: the message gets turned into a pseudo-mime message with the following headers: MIME-Version: 1.0 Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Description: clearsigned data Content-Disposition: inline You'll note that this becomes "quoted-printable", meaning it will have lots of embedded "=20" and similar items [usually at the tail end of a line that wrapped as I wrote it...] Viewing the "plain text" of the message itself, I see that the sig line WAS changed: =2D----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [...] =2D --=20 Yet another Blog: http://osnut.homelinux.net =2D----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+ci8PV/YHUqq2SwsRAhM6AKDJ2L547zqiCYAHfCEEgaggH0svyACgwRTS riVuATN0kZRGJyd5QfgF6QY=3D =3Dm4sq =2D----END PGP SIGNATURE----- Notice that any line that begins with a "-" becomes "=2D" followed by more dashes. This appears to have "broken" the sig seperator because it becomes "=2D<space><dash><dash>=20", hence the reported "- --<space>" I'm hesitant to report this to the kmail group as a "bug" because it appears that this may be a known, and possibly moot, issue: the "developers" appear to be using version 1.5.9 [the released version is 1.5.0] and they all seem to have "detached" signatures, so "this may already be fixed" [but I'm not running the developer version, so you'll have to live with my "buggy" sig line -- fortunately I keep it fairly short :) ] Of course, veering back to the original topic [8.2 announced], one of the features of 8.2 is the inclusion of KDE 3.1, meaning that "all of a sudden" lots of people will start using kmail 1.5, and I'm reasonably certain it will be 1.5.0, not 1.5.9 or better ;) [but of this is only a hiccup when signing messages, the occurance rate of "buggy" sig seperators should be fairly low - -- did any of my previous messages appear "broken" before I started using the signing capability?] Tom - -- Yet another Blog: http://osnut.homelinux.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQE+cj+PV/YHUqq2SwsRAoMCAKDBhJkK869AClfcyitNxRLZJ8OA9gCgo5Ba UFhqj9ZdAikK/lLB2IA6Q0o= =0euh -----END PGP SIGNATURE-----