Thus spake Paul Johnson: > When I responded to the message, it also tried to reply using s/mime. > This is functionality I don't ever recall seeing documentation for. > I'm wondering if it's worth bothering fixing this, and if it is, how > to go about doing so. I couldn't get a good starting place trying to > google for it, hopefully an OpenSSL guru can devine something from > those bizarre runes. To start off, you'll need a certificate authority bundle... apt-file tells me of a few packages in unstable which ship such a file: kdelibs-data: usr/share/apps/kssl/ca-bundle.crt libapache-mod-ssl: etc/apache/ssl.crt/ca-bundle.crt libcurl2: usr/share/curl/curl-ca-bundle.crt sympa: usr/share/sympa/ca-bundle.crt Likely, libcurl2 will already be installed, so you should be able to either copy /usr/share/curl/curl-ca-bundle.crt to ~/.smime/ca-bundle.crt, symlink it, or in your .muttrc: set smime_ca_location="/usr/share/curl/curl-ca-bundle.crt" That'll at least get you a bit farther along...I believe you'd then be able to view S/MIME messages without seeing those icky errors... sending them would be another story, however. -- Nathan Poznick <poznick@conwaycorp.net> The reason the way of the transgressor is hard is because it's so crowded. - Kin Hubbard
Attachment:
pgp4DPeK1zWOQ.pgp
Description: PGP signature