Gary --
...and then Gary said...
% Hello all,
% I have just switched over to GPG instead of PGP, as PGP 6.52 would not
Woo hoo! Welcome :-)
% work properly. The new GPG installed well, but I cannot get is
% properly scripted (for a lack of knowledge) in my muttrc file.
Hmmm... How so, I wonder? Or are you, as was I, just baffled and too
nervous to get started? :-)
%
% Can someone help, or point me in the right direction for a sample
% script on line? Could not find any references in the sample rc files
% on line.
Charles Curley would say that it all works right out of the box, but I
didn't believe him when I first tried it. All in all, though, he's quite
right :-)
Check your tarball's contrib dir for a gpg.rc file; copy that file into
your ~/.mutt (or wherever you have your muttrc files; if you have only
one as ~/.muttrc, you might want to call this ~/.muttrc.gpg or some
such). Source this file somewhere in your muttrc (more on that later).
You may want to make a few changes; I did. I had to get rid of the
gpg-2comp "arg" in each of the pgp_* command definitions since I don't
have that; IIRC, that is how you get gpg to generate sigs/crypts that are
compatible with pgp2 instead of pgp5 and up. That was about it, though,
thanks to some changes in my gpg options file. And, so, ...
On to your gpg options file, found as ~/.gnupg/options. This is generated
automatically the first time you run gpg, so run it once and then fire
up your editor. You very well might want to set your default-key and
encrypt-to settings; the former is obvious, but you will note that setting
the latter to your keyid will ensure that you can read any message you
send out (by also encrypting the message to your public key). [You can
now save a cleartext fcc instead, and that would not only make your sent
messages smaller but also keep your keyid out of them, but this is what
worked for me; I want my local copy encrypted.] You'll probably want to
set no-greeting and even no-secmem-warning if your gpg is not installed
sgid; after all, you know by now that it is using insecure memory :-)
Hokay, then; back to your muttrc file. If you were using pgp with a mutt
before 1.x (as I was), then you'll have some cleaning to do; the old
vars pgp_encryptself, pgp_v2, pgp_v5, pgp_gpg, and pgp_default_version
are gone now (and that first one is why you want to set your encrypt-to
option; it's also easier than specifying the extra recipient in all of
the encrypt commands in gpg.rc). Anyway, you'll know that all is well
if you fire up mutt and it doesn't tell you about bad variables!
Once you have your muttrc sourcing gpg.rc (this is handy not only because
it unclutters your muttrc but also because you can use a single hook
to then source any encryption rc file; maybe you want to use pgp2 when
trading mail with person X but gpg otherwise...) successfully, you should
be able to send signed and/or encrypted email pretty painlessly. You can
now even send old-style signatures; setting "pgp_create_traditional"
causes mutt to use pgp_clearsign_command instead of pgp_sign_command :-)
%
% Thanks for your help,
HTH & HAND
%
% Regards,
% Gary
:-D
--
David T-G * It's easier to fight for one's principles
(play) [EMAIL PROTECTED] * than to live up to them. -- fortune cookie
(work) [EMAIL PROTECTED]
http://www.bigfoot.com/~davidtg/ Shpx gur Pbzzhavpngvbaf Qrprapl Npg!
The "new millennium" starts at the beginning of 2001. There was no year 0.
Note: If bigfoot.com gives you fits, try sector13.org in its place. *sigh*
PGP signature
