Gnus development mailing list
 help / color / mirror / Atom feed
From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: gpg-ring.el/gpg.el?
Date: Wed, 21 Nov 2001 10:05:16 -0500	[thread overview]
Message-ID: <87vgg4mafn.fsf@mclinux.com> (raw)
In-Reply-To: <86wv0lgp4s.fsf@duchess.twilley.org>

Jack Twilley <jmt+usenet@twilley.org> writes:

> What about adding in another key/value pair?
>
> <$secure type=[] mode=[] key=[]>
>
> Where type and mode are as above, and key is the key ID(s) for which
> the message should be encrypted or signed.

Personally, I don't think this is a good idea, since I'd rather look
for the recipients at message send time, not whenever the user chose
to add the secure tag.

My idea for the secure tag was it would be replaced with the
appropriate <$(multi)?part (sign=|encrypt=)> when the mml is
processed, and at that time the key could be chosen.

I don't use S/MIME, but it looks like there is support for specifying
the keys that you use?  Is that true?

ttyl,

-- 
Josh Huber



      reply	other threads:[~2001-11-21 15:05 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-16 19:10 gpg-ring.el/gpg.el? Josh Huber
2001-11-16 20:32 ` gpg-ring.el/gpg.el? Simon Josefsson
2001-11-16 21:19   ` gpg-ring.el/gpg.el? Josh Huber
2001-11-16 21:37     ` gpg-ring.el/gpg.el? Simon Josefsson
2001-11-17 11:10       ` gpg-ring.el/gpg.el? Florian Weimer
2001-11-17 11:43         ` gpg-ring.el/gpg.el? Simon Josefsson
2001-11-19 21:56           ` gpg-ring.el/gpg.el? Florian Weimer
2001-11-20 20:51         ` gpg-ring.el/gpg.el? Werner Koch
2001-11-16 21:38   ` gpg-ring.el/gpg.el? Matt Armstrong
2001-11-19 15:03     ` gpg-ring.el/gpg.el? Josh Huber
2001-11-19 19:18       ` gpg-ring.el/gpg.el? Matt Armstrong
2001-11-19 19:43         ` gpg-ring.el/gpg.el? Josh Huber
2001-11-19 20:05           ` gpg-ring.el/gpg.el? Matt Armstrong
2001-11-20 20:32       ` gpg-ring.el/gpg.el? Jack Twilley
2001-11-21 15:05         ` Josh Huber [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=87vgg4mafn.fsf@mclinux.com \
    --to=huber@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).