On Fri, 19 Mar 2004 14:27:53 EST, you said:
> Valdis.Kletnieks@xxxxxx <Valdis.Kletnieks@xxxxxx>, Nico Golde, Frank Knobbe,
> et al have wonderful things to say and contribute great things to this list,
> but i have never read anything they post because they post as attachments.
PGP signed messages are not executable attachments.
See the following RFCs:
1847 Security Multiparts for MIME: Multipart/Signed and
Multipart/Encrypted. J. Galvin, S. Murphy, S. Crocker, N. Freed.
October 1995. (Format: TXT=23679 bytes) (Status: PROPOSED STANDARD)
2015 MIME Security with Pretty Good Privacy (PGP). M. Elkins. October
1996. (Format: TXT=14223 bytes) (Updated by RFC3156) (Status:
PROPOSED STANDARD)
2440 OpenPGP Message Format. J. Callas, L. Donnerhacke, H. Finney, R.
Thayer. November 1998. (Format: TXT=141371 bytes) (Status: PROPOSED
STANDARD)
3156 MIME Security with OpenPGP. M. Elkins, D. Del Torto, R. Levien,
T. Roessler. August 2001. (Format: TXT=26809 bytes) (Updates RFC2015)
(Status: PROPOSED STANDARD)
http://www.ietf.org/rfc/rfc1847.txt
http://www.ietf.org/rfc/rfc2015.txt
http://www.ietf.org/rfc/rfc2440.txt
http://www.ietf.org/rfc/rfc3156.txt
If anything, you should *encourage* the use of PGP or S/MIME to sign mail,
because even if my machine gets whacked by a virus and starts spewing correctly
signed mail, you will *know* it's my machine doing it and not some
address-scraping virus on a machine in Zanzibar or someplace.
Attachment:
pgp00069.pgp
Description: PGP signature