Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: david.goldberg6@verizon.net (David S. Goldberg)
Subject: Re: Automatic retrieval of certificates (S/MIME)
Date: Mon, 07 Feb 2005 10:46:40 -0500	[thread overview]
Message-ID: <mj7wttk1ig0.fsf@mm117419-pc.MITRE.ORG> (raw)
In-Reply-To: <ilu8y63mep3.fsf@latte.josefsson.org>

>>>>> On Sat, 05 Feb 2005 12:25:12 +0100, Simon Josefsson
>>>>> <jas@extundo.com> said:

>> If/when that happens, would the pgg interface then take care of
>> this?

> No, but a separate Gnus<->gpgsmime interface could be written.

Darn :-)

> Also, the current smime.el could perhaps be extended to use
> password.el to do password caching.

Hmmm.  That might be something even I could try to implement.

>>> You can specify the key/cert in the MML tags, if that is what you
>>> meant.  See 'MML Definition' in the Emacs MIME manual.  You can say,
>>> e.g.:
>> 
>>> <#part sign=smime keyfile="~/cacert.user.key">
>> 
>> I use <#multipart> which ends up being a complete replacement the
>> <#secure> tag in that the signature applies to the entire message.
>> I've never got the <#secure> tat to work if there are multiple
>> recipients.

> It might be a bug.

I've asked about this on the ding-list a couple times over the years.
If there is a bug, it's that, when using the <#secure> tag it only
ever prompts for one key and it never tells you for which recipient
it's prompting.  Last time I brought it up I attempted to understand
the code and add that capability.  I never was able to, and so went
with building my own solution.

-- 
Dave Goldberg
david.goldberg6@verizon.net


      reply	other threads:[~2005-02-07 15:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-27 11:13 Stefan Kamphausen
2005-01-27 18:33 ` Simon Josefsson
2005-01-27 19:31   ` David S. Goldberg
2005-02-05 11:25     ` Simon Josefsson
2005-02-07 15:46       ` David S. Goldberg [this message]

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=mj7wttk1ig0.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).