From: Jack Vinson <jvinson@chevax.ecs.umass.edu>
Subject: Re: MIME and PGP (was: Gnus and Crypto stuff)
Date: 11 Dec 1998 09:55:07 -0600 [thread overview]
Message-ID: <wkg1amfzc4.fsf@chevax.ecs.umass.edu> (raw)
In-Reply-To: Karl Kleinpaste's message of "Fri, 11 Dec 1998 10:14:16 -0500"
>>>>> "KK" == Karl Kleinpaste <karl@justresearch.com> writes:
KK> Jack Vinson <jvinson@chevax.ecs.umass.edu> writes:
>> It looked to me like there should have been about three parts, but
>> that the PGP signature broke the MIME parsing somehow.
KK> Assuming that one wants to PGP-sign an entire message, one needs the
KK> ability for Gnus to MIME-encode the whole thing and then let MailCrypt
KK> do its PGP thing to the result. Similarly, on receipt, we need the
KK> ability to make gnus-article-hide-pgp happen rather early on, followed
KK> by MIME decoding. The fundamental problem we're up against is that,
KK> at least for the recipient, PGP armor is removed rather late in the
KK> game, long after Gnus has reached its conclusions about the MIME
KK> components in the message. PGP needs to be the last thing added and
KK> the first thing removed.
KK> I'm not really sure what semantic would be in order, if one wanted to
KK> PGP-sign individual components of a message, rather than the whole
KK> thing.
At least for message-send, the current set of actions is something like
- fixup the message
- encode the message body
- run message-send-hook
- send the message
- message-header-hook, message-send-mail-hook or
message-send-news-hook
- deal with fcc
- run message-sent-hook
- housekeeping
It looks like message-send-mail/news-hook are run with the final version of
the message (i.e. just before it goes out to the world). I am guess this
is where the pgp stuff *should* be called. But that means adding pgp to
two hooks instead of just one.
As I mentioned earlier, I would like a hook that is called before the
message body is encoded so that things like ispell-message don't have to
deal with the MIME stuff.
--
Jack Vinson <jvinson@chevax.ecs.umass.edu> http://www.cis.upenn.edu/~vinson/
Zippy: I'm shaving!! I'M SHAVING!!
next prev parent reply other threads:[~1998-12-11 15:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <x7vhjjzeg9.fsf@peorth.gweep.net>
1998-12-11 14:22 ` Jack Vinson
1998-12-11 14:36 ` Norbert Koch
1998-12-11 15:14 ` Karl Kleinpaste
1998-12-11 15:55 ` Jack Vinson [this message]
[not found] ` <x7u2z2wvg9.fsf@peorth.gweep.net>
1998-12-11 15:34 ` Karl Kleinpaste
1998-12-11 16:12 ` Robert Bihlmeyer
1998-12-13 8:52 ` Gnus and Crypto stuff Lars Magne Ingebrigtsen
1998-12-17 18:28 ` Jason R Mastaler
1998-12-13 22:50 ` Dave Love
1998-12-13 23:02 ` Hrvoje Niksic
1998-12-14 18:26 ` Dave Love
[not found] ` <x7r9u3mycp.fsf@peorth.gweep.net>
1998-12-15 1:59 ` David Hedbor
1998-12-15 3:15 ` Johan Danielsson
1998-12-15 4:55 ` David Hedbor
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=wkg1amfzc4.fsf@chevax.ecs.umass.edu \
--to=jvinson@chevax.ecs.umass.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).