Re: GPG Signature
I don't know whether you want to include a lot of gpg usage information in your howto on Mutt and GPG but here's what I had to do to export my key to the key server and validate that it was exported.
Assuming that the key is created already which may be a big assumption:
gpg --keyserver wwwkeys.pgp.net --send-keys eric
gpg --list-keys eric
gpg --recv-keys 0xA0EBA1B6
The first line updates the specified keyserver with the key for the person whose first name is specified (in this case, me).
The second line lists the values for the person specified (first name) so that they key id can be retrieved. I knew what value to look at from looking at your key and documentation and deducing it.
The third line retrieves the key from the keyserver, thus validating that the key was successfully updated to the keyserver by line 1.
I'd be happy to draft a paragraph on generating a key if you wanted to get to that level of detail and thought it might be helpful.
I also attempted to use keyserver pgp.ai.mit.edu and got the message that:
gpg: can't connect to `pgp.ai.mid.edu': Connection refused
I also attempted to use keyserver search.keyserver.net and got the message:
gpg: error sending to `search.keyserver.net': eof
I really appreciate your Howto. Its the best explanation on the whole signing/encrypting/securing of email that I've read.
Eric [eric@dimension11.net www.dimension11.net]
On Sun, Nov 18, 2001 at 10:04:35PM -0500, Justin R. Miller wrote:
> Thus spake Eric Brooks (eric@dimension11.net):
>
> > Your tutorial on GnuPG with Mutt is awesome. Much appreciated! I'm
> > going to work through it and get myself setup.
>
> Thanks, glad you like it! I'll probably have some updates soon as well.
> Just a couple of notes as you get into it:
>
> 1. There are one or two features that are specific to Mutt 1.3.x. You
> might want to give it a shot, as it is in its second or third beta now
> for 1.4. I used 1.2.5 for about a day or two, but was using IMAP at the
> time, so I upgraded to the unstable tree to benefit from some IMAP
> enhancements, and the document reflects this.
>
> 2. Some people, especially Outlook users, are picky about the way Mutt
> does PGP signatures. Basically, Mutt defaults to PGP/MIME, which means
> that the signature is a MIME attachment instead of inline. You can use
> pgp_create_traditional to make it inline, but Mutt (properly, I might
> add) uses a content-type (I forget what) that is not text/plain, and
> Outlook still behaves weirdly. You can patch Mutt for Outlook
> compatibility, but that's not on my list of important stuff to do ;-)
> Anyway, in the document I'm a little loose on the terminology and
> basically say that Mutt uses PGP/MIME, which is the "new way" of doing
> things. Long threads on both the Mutt and GnuPG mailing lists show many
> peoples' inputs on both sides of that issue and how it should be
> handled.
>
> Otherwise, thanks again for the feedback and good luck!
>
> --
> Justin R. Miller <incanus@codesorcery.net>
> PGP/GnuPG Key ID 0xC9C40C31 (preferred)
Reply to: