* best approach to S/MIME?
@ 2013-03-15 20:22 Greg Troxel
2013-03-16 0:47 ` James Cloos
2013-03-18 9:34 ` Daiki Ueno
0 siblings, 2 replies; 4+ messages in thread
From: Greg Troxel @ 2013-03-15 20:22 UTC (permalink / raw)
To: ding
[-- Attachment #1: Type: text/plain, Size: 728 bytes --]
I am trying to get set up with S/MIME. I have no personal cert yet, but
I have imported a correspondent's key and CA cert and marked the CA
trusted. gpgsm on the command line will verify a message.
I read this:
http://www.emacswiki.org/emacs/GnusSMIME
and set: (setq mml-smime-use 'epg)
which seems to be the default these days if epg exists.
(I am using gnus from git master, via load-path, and emacs 23.4.1.)
But I still get "No CA configured" when displaying a message (which is
really a base-64 encoded s/mime signed message).
This is in smime-verify-region which is the openssl variant.
Can someone tell me what the best thing to do is for S/MIME? (I have
been happily using OpenPGP with epg for many years.)
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: best approach to S/MIME?
2013-03-15 20:22 best approach to S/MIME? Greg Troxel
@ 2013-03-16 0:47 ` James Cloos
2013-03-18 9:34 ` Daiki Ueno
1 sibling, 0 replies; 4+ messages in thread
From: James Cloos @ 2013-03-16 0:47 UTC (permalink / raw)
To: Greg Troxel; +Cc: ding
>>>>> "GT" == Greg Troxel <gdt@work.lexort.com> writes:
GT> I am trying to get set up with S/MIME.
I customized this:
'(smime-CA-directory "/etc/ssl/certs")
to get gnus to verify smime-signed incoming messages.
I haven't needed to use smime for outgoing mail, and so haven't tested
that aspect at all.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 1024D/ED7DAEA6
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: best approach to S/MIME?
2013-03-15 20:22 best approach to S/MIME? Greg Troxel
2013-03-16 0:47 ` James Cloos
@ 2013-03-18 9:34 ` Daiki Ueno
2013-03-18 11:22 ` Greg Troxel
1 sibling, 1 reply; 4+ messages in thread
From: Daiki Ueno @ 2013-03-18 9:34 UTC (permalink / raw)
To: Greg Troxel; +Cc: ding
Greg Troxel <gdt@work.lexort.com> writes:
> and set: (setq mml-smime-use 'epg)
>
> which seems to be the default these days if epg exists.
>
> (I am using gnus from git master, via load-path, and emacs 23.4.1.)
>
> But I still get "No CA configured" when displaying a message (which is
> really a base-64 encoded s/mime signed message).
>
> This is in smime-verify-region which is the openssl variant.
This looks strange indeed. Could you try "M-x debug-on-entry
smime-verify-region" to check the code path?
Regards,
--
Daiki Ueno
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: best approach to S/MIME?
2013-03-18 9:34 ` Daiki Ueno
@ 2013-03-18 11:22 ` Greg Troxel
0 siblings, 0 replies; 4+ messages in thread
From: Greg Troxel @ 2013-03-18 11:22 UTC (permalink / raw)
To: Daiki Ueno; +Cc: ding
[-- Attachment #1: Type: text/plain, Size: 591 bytes --]
Debugger entered--entering a function:
* smime-verify-region(1 8835)
mm-view-pkcs7-verify((#<buffer *mm*> ("application/pkcs7-mime" (smime-type .$
mm-view-pkcs7((#<buffer *mm*> ("application/pkcs7-mime" (smime-type . "signe$
mm-possibly-verify-or-decrypt((#<buffer *mm*>
("application/pkcs7-mime" (smi$
mm-dissect-buffer(nil t)
gnus-display-mime()
gnus-article-prepare-display()
gnus-article-prepare(81567 nil)
gnus-summary-display-article(81567)
gnus-summary-next-page(nil)
call-interactively(gnus-summary-next-page nil nil)
Greg Troxel <gdt@work.lexort.com>
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2013-03-18 11:22 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2013-03-15 20:22 best approach to S/MIME? Greg Troxel
2013-03-16 0:47 ` James Cloos
2013-03-18 9:34 ` Daiki Ueno
2013-03-18 11:22 ` Greg Troxel
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).