Gnus development mailing list
 help / color / mirror / Atom feed
From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: How does one pgp/mime encrypt to different recipients?
Date: Wed, 04 Sep 2002 10:46:36 -0400	[thread overview]
Message-ID: <87ofbdizhv.fsf@mail.paradoxical.net> (raw)
In-Reply-To: <u8zit1l3lk9.fsf@blackbird-2k.MITRE.ORG>

David S Goldberg <david.goldberg6@verizon.net> writes:

> Does/should this work for s/mime?  If so what's the syntax for the
> tag?  I've been completely unable to encrypt to multiple recipients
> using the secure tag.  I always have to remember to use
> mml-secure-encrypt-smime which only encrypts a single part, which
> works for my simple text messages, but is clearly not the desired
> approach.

I think it should work for s/mime, but I don't use it.  With s/mime do
you have to specify the recipeints each time, or can it look up based
on the recipient addresses in the headers?

I see now...(looking at mml-smime.el)

Right now I'm not calling the mml-smime-(sign|encrypt)-query
function. 

I don't have smime keys set up to test this, so could you try out this
patch?

Index: mml-sec.el
===================================================================
RCS file: /usr/local/cvsroot/gnus/lisp/mml-sec.el,v
retrieving revision 1.15
diff -u -r1.15 mml-sec.el
--- mml-sec.el	2002/05/08 16:12:53	1.15
+++ mml-sec.el	2002/09/04 15:20:26
@@ -161,7 +161,12 @@
 ;; defuns that add the proper <#secure ...> tag to the top of the message body
 (defun mml-secure-message (method &optional modesym)
   (let ((mode (prin1-to-string modesym))
-	insert-loc)
+	insert-loc
+        (recipients (funcall (nth 2 (assoc method
+                                           (if (or (eq modesym 'sign)
+                                                   (eq modesym 'signencrypt))
+                                               mml-sign-alist
+                                             mml-encrypt-alist))))))
     (mml-unsecure-message)
     (save-excursion
       (goto-char (point-min))
@@ -170,7 +175,7 @@
 	     (goto-char (setq insert-loc (match-end 0)))
 	     (unless (looking-at "<#secure")
 	       (mml-insert-tag
-		'secure 'method method 'mode mode)))
+		'secure 'method method 'mode mode recipients)))
 	    (t (error
 		"The message is corrupted. No mail header separator"))))
     (when (eql insert-loc (point))


If that doesn't work, can you tell me what the mml-smim-sign-query
function returns for you?  Does it include the "recipients" symbol?

Thanks,

-- 
Josh Huber



  reply	other threads:[~2002-09-04 14:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-02 18:33 John A. Martin
2002-09-02 20:07 ` Simon Josefsson
2002-09-02 22:38   ` John A. Martin
2002-09-03  9:45     ` Kai Großjohann
2002-09-03 14:52     ` Josh Huber
2002-09-04 13:56       ` David S Goldberg
2002-09-04 14:46         ` Josh Huber [this message]
2002-09-05 16:53           ` David S Goldberg
2002-09-05 17:05             ` Josh Huber
2002-09-06 15:22               ` David S Goldberg
2002-09-03 16:10     ` Simon Josefsson

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=87ofbdizhv.fsf@mail.paradoxical.net \
    --to=huber@alum.wpi.edu \
    --cc=huber+dated+1031581406.8bcd7a@alum.wpi.edu \
    /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).