From: david.goldberg6@verizon.net (David S. Goldberg)
Subject: #secure smime signencrypt not working to myself
Date: Tue, 01 Mar 2005 11:29:33 -0500 [thread overview]
Message-ID: <mj7650bwcr6.fsf@mm117419-pc.MITRE.ORG> (raw)
A while back I posted my method for doing smime encryption and
signatures by building a multipart around the entire message and call
mml-secure-encrypt-smime and mml-secure-sign-smime and going through
the headers to insert the appropriate key and cert files. The recent
changes made to gnus' smime functionality encouraged me to try to work
in a more "standard" fashion so I set up mml-encrypt-alist to use my
function to traverse the headers and determine the appropriate key and
cert files (I still haven't had much luck with the new ldap interface,
probably because I use XEmacs) without prompting when I run
mml-secure-message-encrypt-smime and it works mostly great with one
exception. Messages either sent to my self via mail or gcc are not
readable. I get an error: Could not identify PKCS#7 type.
Thunderbird is also unable to read the message so it's not just some
weird limitation in gnus. On the command line I'm able to pipe
openssl smime -decrypt to openssl smime -verify to read the message.
Go figure. mml-signencrypt-style-alist is the default with smime set
to separate, but it's apparently not equivalent to having two mode
tags in the #secure which is just as well since #secure only seems to
be willing to recognize one mode tag anyway. Any thoughts on how to
track this down?
Thanks,
--
Dave Goldberg
david.goldberg6@verizon.net
next reply other threads:[~2005-03-01 16:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 16:29 David S. Goldberg [this message]
2005-03-06 21:14 ` Arne Jørgensen
2005-04-13 12:44 ` Ldap certificate retrieval in XEmacs (was: #secure smime signencrypt not working to myself) Arne Jørgensen
2005-04-14 11:27 ` Ldap certificate retrieval in XEmacs Arne Jørgensen
2005-04-14 11:41 ` Arne Jørgensen
2005-04-26 12:07 ` Arne Jørgensen
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=mj7650bwcr6.fsf@mm117419-pc.MITRE.ORG \
--to=david.goldberg6@verizon.net \
/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).