From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: Decoding application/x-pkcs7-mime?
Date: Tue, 16 Sep 2008 10:51:47 +0200 [thread overview]
Message-ID: <kz4p4giicc.fsf@kafka.physik3.gwdg.de> (raw)
In-Reply-To: <m2zlm9sd07.fsf@nwalsh.com> (Norman Walsh's message of "Mon, 15 Sep 2008 10:24:40 -0400")
Norman Walsh <ndw@nwalsh.com> writes:
> One of my colleagues has started sending mail signed as follows:
>
> Content-Type: application/x-pkcs7-mime;smime-type=signed-data;name=smime.p7m;
> smime-type=signed-data;
> name="smime.p7m"
> Content-Transfer-Encoding: base64
> Content-Disposition: attachment;
> filename="smime.p7m"
> Content-class: urn:content-classes:message
This looks like signed and encrypted? A purely signed message usually
has a part
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"
Content-Description: S/MIME Cryptographic Signature
Anyway. Do you have something like
(add-to-list 'gnus-newsgroup-variables '(gnus-buttonized-mime-types . '("multipart/encrypted" "multipart/signed" "multipart/alternative")))
(setq mm-decrypt-option 'always)
(setq mm-verify-option 'always)
in your .gnus?
Some time ago, I've written up my quest to get S/MIME to work in Gnus on
the EmacsWiki:
http://www.emacswiki.org/cgi-bin/wiki/GnusSMIME
I guess this is not up-to-date anymore, but it might still work. I also
remember trying to use EPG and gnutls, but it didn't work at that
time. If someone succesfully uses S/MIME with those, I'd love to see an
example setup.
-David
next prev parent reply other threads:[~2008-09-16 8:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-15 14:24 Norman Walsh
2008-09-16 8:15 ` Steinar Bang
2008-09-16 8:23 ` Steinar Bang
2008-09-16 8:51 ` David Engster [this message]
2008-09-16 9:23 ` Rupert Swarbrick
2008-09-16 9:34 ` David Engster
2008-09-16 9:42 ` Rupert Swarbrick
2008-09-17 7:16 ` Daiki Ueno
2008-09-17 10:34 ` David Engster
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=kz4p4giicc.fsf@kafka.physik3.gwdg.de \
--to=deng@randomsample.de \
--cc=ding@gnus.org \
/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).