first, start out with this:
http://www.ezitrust.com/guides/mutt.pdf
before following its directions blindly, get the smime.rc from the mutt
distribution (it's in /usr/share/doc/mutt-verision/samples on my distro)
included in your muttrc file first, before following the directions in
that file.
that will get you to the point where you can encrypt & sign messages
using s/mime. you will also be able to decrypt & verify messages sent
from other mutt users.
but, if you receive an s/mime message from a user of another MUA, mutt
may have problems. it seems that current versions of mutt expect the
mime types of smime messages to be application/x-pkcs7-signature
and application/x-pkcs7-mime, whereas many other MUAs use
application/pkcs7-signature (for signed) and application/pkcs7-mime for
encrypted messages.
I found two bugs posted about this at mutt.org, bug #1644 and #1685.
you can see the text of the bugs at http://bugs.guug.de/db/pa/lmutt.html
There is a patch included in one of those two bugs which allows mutt to
recognize both application/pkcs7-signature and application/x-pkcs7-signature.
That allows mutt to handle smime signatures.
I believe the patch should be expanded to do something similar for
encrypted messages. my temporary solution is to use procmail to hack the
headers of the message so mutt sees its expected mime type.
here's the details of my hack.
mutt expects to see: Content-Type: application/x-pkcs7-mime;
smime-type=enveloped-data;
name="smime.p7m"
(I didn't start the 'Content-Type' at the beginning of the line just to
make sure it didn't look like a header)
but mail.app in OS X instead puts this: Content-Type: application/pkcs7-mime;
name=smime.p7m
So I added a procmail rule at the top of my list of rules:
:0 fhw
* ^Content-Type: application/pkcs7-mime; name=smime.p7m
| formail -I "Content-Type:" -X "" ; cat $HOME/.procmail/smimeHeaders.txt ; echo
the smimHeaders.txt just contains the header mutt wants to see. the -I
part deletes the existing Content-Type header.
good luck.
On Fri, Jan 09, 2004 at 09:13:08PM -0600, Michael D Schleif wrote:
> As you know, I am a gpg user. I have an acquaintance who uses s/mime.
>
> With gpg/pgp, we have the local keyrings, and I can use somebodies
> public key to encrypt a message to him.
>
> I have not found away to save/store this acquaintance's certificate/key
> information.
>
> How do I encrypt a message to this person, that he can decrypt?
>
> What do you think?
>
> --
> Best Regards,
>
> mds
> mds resource
> 877.596.8237
> -
> Dare to fix things before they break . . .
> -
> Our capacity for understanding is inversely proportional to how much
> we think we know. The more I know, the more I know I don't know . . .
> --
Attachment:
smime.p7s
Description: S/MIME cryptographic signature