David J. Weller-Fahy wrote: > After much frustration I discovered why mutt wouldn't work with the > SMIME keys issued at work: there are two of the private keys (one for > signature, one for encryption), and a single public key. As I have an > employer that is more than willing to let me use mutt (if I can get it > to work properly) I am inclined to do whatever I can to get signing and > encryption functional! > > I've always used GPG for email encryption and am not familiar with SMIME > use in mutt, so I have some questions: > > Is this a supported configuration? If so, does anyone have an example > configuration they'd like to share?
Hi David, I don't use S/MIME either, so I hope you'll pardon me if this isn't helpful. To start, my impression was that (like GPG) encryption usually uses the recipients key, not your own key. You'll usually use your own key just for signing and decryption. That said, I would suggest looking into customizing the $smime_encrypt_command, $smime_sign_command, and $smime_decrypt_command options inside your .muttrc. By default, they use the placeholders shown in http://dev.mutt.org/doc/manual.html#smime-decrypt-command for specifying the default key (%k) or recipient keys (%c). But nothing stops you from hardcoding values in your muttrc. Sample values for smime are usually packaged with mutt, but you can also refer to http://dev.mutt.org/hg/mutt/file/tip/contrib/smime.rc -Kevin
signature.asc
Description: PGP signature
