From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/4424 Path: news.gmane.org!not-for-mail From: david.goldberg6@verizon.net (David S. Goldberg) Newsgroups: gmane.emacs.gnus.user Subject: Re: Automatic retrieval of certificates (S/MIME) Date: Mon, 07 Feb 2005 10:46:40 -0500 Organization: I Yam What I Yam Message-ID: References: <85vf9jw2e2.fsf@news.individual.de> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138670344 23188 80.91.229.2 (31 Jan 2006 01:19:04 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 01:19:04 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:33:44 2006 Original-Path: quimby.gnus.org!newsfeed1.e.nsc.no!news.tele.dk!news.tele.dk!small.news.tele.dk!newsfeed.news2me.com!arclight.uoregon.edu!news.tufts.edu!newstransit.mitre.org!news.mitre.org!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: blackbird.mitre.org Original-X-Trace: newslocal.mitre.org 1107791212 16359 129.83.50.102 (7 Feb 2005 15:46:52 GMT) Original-X-Complaints-To: news@mitre.org Original-NNTP-Posting-Date: Mon, 7 Feb 2005 15:46:52 +0000 (UTC) Mail-Copies-To: nobody User-Agent: Gnus/5.110003 (No Gnus v0.3) XEmacs/21.4.15 (cygwin32) Cancel-Lock: sha1:1dymnca9Ad8NZfIkbD3HNYzXL5U= Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:4565 Original-Lines: 38 X-Gnus-Article-Number: 4565 Tue Jan 17 17:33:44 2006 Xref: news.gmane.org gmane.emacs.gnus.user:4424 Archived-At: >>>>> On Sat, 05 Feb 2005 12:25:12 +0100, Simon Josefsson >>>>> 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