From: "Matt Armstrong" <matt+dated+1008792310.0c091d@lickey.com>
Subject: Re: gpg-ring.el/gpg.el?
Date: Mon, 19 Nov 2001 13:05:07 -0700 [thread overview]
Message-ID: <87k7wmle6k.fsf@squeaker.lickey.com> (raw)
In-Reply-To: <87herqeecu.fsf@mclinux.com> (Josh Huber's message of "Mon, 19 Nov 2001 14:43:13 -0500")
Josh Huber <huber@alum.wpi.edu> writes:
> "Matt Armstrong" <matt+dated+1008789496.23e4db@lickey.com> writes:
>
>> It could be done during a pre-processing run -- if a $secure tag is
>> <snip>
>
> Right, but I think you wouldn't need to do explicitly sign each
> part. Personally, the behavior I'd be looking for would be the
> automatic wrapping of the whole message with a multipart/mixed part,
> and then signing that part.
Yes, I agree completely. The current per-part signing and encryption
controls should still be available for the power users. But most
folks think of signing and encryption as an attribute of the whole
message, so a global flag is a better default.
--
matt
next prev parent reply other threads:[~2001-11-19 20: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 ` Matt Armstrong [this message]
2001-11-20 20:32 ` gpg-ring.el/gpg.el? Jack Twilley
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=87k7wmle6k.fsf@squeaker.lickey.com \
--to=matt+dated+1008792310.0c091d@lickey.com \
/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).