From: Norman Walsh <ndw@nwalsh.com>
Subject: smime?
Date: Mon, 12 Sep 2005 09:57:51 -0400 [thread overview]
Message-ID: <8764t68k2o.fsf@nwalsh.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2887 bytes --]
One of my colleagues has started using S/MIME to sign messages.
But when I try to read them, gnus (5.10.7) goes bang:
Debugger entered--Lisp error: (error "Invalid argument 3")
call-process-region(1 7396 nil nil ("*OpenSSL output*" t) nil "smime" "-verify" "-noverify" "-out" "/dev/null")
apply(call-process-region 1 7396 nil nil ("*OpenSSL output*" t) nil ("smime" "-verify" "-noverify" "-out" "/dev/null"))
smime-call-openssl-region(1 7396 ("*OpenSSL output*" t) "smime" "-verify" "-noverify" "-out" "/dev/null")
smime-noverify-region(1 7396)
smime-noverify-buffer()
mml-smime-verify(((#("multipart/mixed" 0 15 ...) (#<buffer *mm*<13>> ... 7bit nil nil nil nil nil) (#<buffer *mm*<14>> ... 7bit nil ... nil nil nil)) (#<buffer *mm*<15>> ("application/x-pkcs7-signature" ...) base64 nil ("attachment" ...) "S/MIME Cryptographic Signature" nil nil)) (#("multipart/signed" 0 16 (start nil from "colleague@host.com" buffer #<buffer *mm*<11>> boundary "------------ms070502010904030200030703" micalg "sha1" protocol "application/x-pkcs7-signature")) (protocol . "application/x-pkcs7-signature") (micalg . "sha1") (boundary . "------------ms070502010904030200030703")))
mm-possibly-verify-or-decrypt(((#("multipart/mixed" 0 15 ...) (#<buffer *mm*<13>> ... 7bit nil nil nil nil nil) (#<buffer *mm*<14>> ... 7bit nil ... nil nil nil)) (#<buffer *mm*<15>> ("application/x-pkcs7-signature" ...) base64 nil ("attachment" ...) "S/MIME Cryptographic Signature" nil nil)) (#("multipart/signed" 0 16 (start nil from "colleague@host.com" buffer #<buffer *mm*<11>> boundary "------------ms070502010904030200030703" micalg "sha1" protocol "application/x-pkcs7-signature")) (protocol . "application/x-pkcs7-signature") (micalg . "sha1") (boundary . "------------ms070502010904030200030703")))
mm-dissect-multipart((#("multipart/signed" 0 16 (start nil from "colleague@host.com" buffer #<buffer *mm*<11>> boundary "------------ms070502010904030200030703" micalg "sha1" protocol "application/x-pkcs7-signature")) (protocol . "application/x-pkcs7-signature") (micalg . "sha1") (boundary . "------------ms070502010904030200030703")) "colleague@host.com")
mm-dissect-buffer(nil nil)
gnus-display-mime()
gnus-article-prepare-display()
gnus-article-prepare(8170 nil)
gnus-summary-display-article(8170)
gnus-summary-next-page(nil)
* call-interactively(gnus-summary-next-page)
My best guess is that smime.el is trying to run a program called "smime".
What is that and where do I get it? Or how do I make this error go away,
in any event?
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | 'Tis better to be silent and be thought
http://nwalsh.com/ | a fool, than to speak and remove all
| doubt.--Abraham Lincoln
[-- Attachment #2: Type: application/pgp-signature, Size: 188 bytes --]
next reply other threads:[~2005-09-12 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 13:57 Norman Walsh [this message]
2005-09-12 14:13 ` smime? Norman Walsh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8764t68k2o.fsf@nwalsh.com \
--to=ndw@nwalsh.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).