Re: can sign from PGP menu but not from S/MIME menu
Hi,
* rj wrote:
When I try to "(s)ign" an outgoing message from the S/MIME menu ("S" from
within the Compose Menu), I'm getting this warning: "Can't sign: No key
specified. Use Sign As."
And when I try to "sign (a)s" from the S/MIME menu, I get this warning:
"/.index: No such file or directory (errno = 2)" .
By contrast, when I sign or sign-as from the PGP menu ("p" from
the Compose Menu), things work as they should.
I have a .gpg.rc file, and in my .muttrc I have:
source ~/.gpg.rc
In both my .muttrc and my .gpg.rc I have:
set pgp_sign_as=fc5c7370
In my .gnupg/options file I have:
default-key FC5C7370
Your mutt -v output says you don't use gpgme for crypto, i.e. you use
gpg/pgp-interface for PGP-compatible crypto and OpenSSL for S/MIME
crypto.
You only configured the PGP part with these settings, not the OpenSSL
part. You need to tell mutt where you're certificates are and what your
S/MIME key is and probably how to call OpenSSL (analogous to
gpg.rc). Please check the S/MIME docs, $smime_certificates and
$smime_default_key.
Also, the fact that we "source .gpg.rc" in the .muttrc makes me wonder if
it might also be necessary to somehow source the ".gnupg/options" file from
the .muttrc as well.
Or is the ".gnupg/options" file read by mutt automatically because it is in
the .gnupg directory? Thanks for any tips.
.gnupg/options contains the configuration for gnupg but not for mutt
(please try sourcing that file next time before asking because it would
have given you tons of syntax errors and answered that question easily).
The file gpg.rc for mutt in contrib just gives you a bridge between
gnupg's command line interface and mutt expectations from a crypto tool.
Rocco