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

Robert Brown said:

> I'd like more information.
> 
> I use pgp 2.6.X and pgpsendmail.  I do not use gpg because I thought that
> I cannot use the public keyservers with it.  Is this correct?

No, I use the public key servers with GPG all the time.  GPG even
has built-in support for obtaining keys directly from a keyserver, as
well as uploading your key to a key server.  It's pretty cool.


> Also, is there something like pgpsendmail for gpg?  I noticed that the
> messages below have attachments.  Is there a way to automatically encrypt
> and/or sign all messages sent, perhaps as an S/MIME attachment?  (Are the
> attachments below S/MIME attachments?  I have never seen one so I don't
> know.)

I'm not familiar with pgpsendmail...

The attachments to many of my earlier messages were in compliance with
the PGP MIME RFC (which I believe is RFC 2440, but I could be
mistaken--if it matters let me know, and I'll find out for certain).
This is how mutt (my mailer, http://www.mutt.org) supports PGP in
messages, for the reason that it is (arguably) the "right" way to do
it.  This is because PGP using clear text has trouble properly
handling non-english languages with non-western-european characters.
PGP MIME handles that situation well and properly.

However, since virtually no mailer on the planet besides mutt does
this properly (emacs and exmh excepted AFAIK), I've patched mutt with
a patch that allows it to do clearsigning of my messages.  My
signature on more recent messages uses that format.


- -- 
Derek Martin
Senior System Administrator
Mission Critical Linux
martin@MissionCriticalLinux.com

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7xF4JdjdlQoHP510RAjXMAKCjLk/tbc8USbr3/Iy1UoF055oLRQCeLiEt
rgRVv2sE2JGpJqd69NIfDRk=
=ouTH
-----END PGP SIGNATURE-----
-
Subcription/unsubscription/info requests: send e-mail with
"subscribe", "unsubscribe", or "info" on the first line of the
message body to discuss-request@blu.org (Subject line is ignored).