From: Jack Twilley <jmt+usenet@twilley.org>
Subject: Re: gpg-ring.el/gpg.el?
Date: Tue, 20 Nov 2001 12:32:03 -0800 [thread overview]
Message-ID: <86wv0lgp4s.fsf@duchess.twilley.org> (raw)
In-Reply-To: <87bshyvm55.fsf@mclinux.com>
>>>>> "Josh" == Josh Huber <huber@alum.wpi.edu> writes:
Josh> I think we need some kind of flag to instruct MML to do the
Josh> right thing, at sending time. Perhaps a new MML tag?
Josh> <$secure type=(sign|encrypt|encryptsign)
Josh> mode=(pgp1991|pgp2015|smime)>
Josh> ... message body ...
Josh> Then, the right thing could be done at sending time (or whenever
Josh> MML is parsed)
Josh> what do you think?
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.
Josh> -- Josh Huber
Jack.
--
Jack Twilley
jmt at twilley dot org
http colon slash slash www dot twilley dot org slash tilde jmt slash
next prev parent reply other threads:[~2001-11-20 20:32 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 ` Jack Twilley [this message]
2001-11-21 15:05 ` gpg-ring.el/gpg.el? Josh Huber
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=86wv0lgp4s.fsf@duchess.twilley.org \
--to=jmt+usenet@twilley.org \
/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).