2000-02-16-16:51:43 Adam Sherman:
> I have --armor in the gpg sign command... Why is this happening?
Beats the heck out of me. I'm using mutt-1.0, which has custom
support or gpg, which works fine; for signing to work all I needed
was (in muttrc):
set pgp_default_version=gpg
set pgp_autosign
set pgp_sign_as="CE34B136"
For encryption, I also set encrypt-to in .gnupg/options so I could
decrypt my Fccs. Since I only have one secret key, I didn't have to
set default-key.
No mention of algorithms, no explicit gpg sign command, nothing.
If you're using a mutt-1.1 version, I think they completely changed
the interface, in an attempt to keep from having to adjust the code
for each pgp varient; so there's a gpg.rc that you should include.
Are you using that? Have you posted the changes you made from the
stock gpg.rc to the mutt list? I don't know anything about the 1.1
stuff, so can't help there.
-Bennett
PGP signature
