PGP Encrypted Mailing Lists (FYI)

PGP Encrypted Mailing Lists (FYI)

[Steven L Baur]

Gnus & Mailcrypt make reading PGP encrypted mailing lists almost as
easy as reading regular lists.  Somebody has implemented a
PGPmajordomo which returns articles in the following format (after
decryption):

The Subject: is constant, and the From: is always from the list owner.

From: Original Author
Date: Original standard date
###################### Encrypted Message #######################

(Original article appears here)

################################################################

[Block of PGP output garbage]

########## Clear Text header as received by Majordomo ##########
[Original clear text headers including In-Reply-To: and References:]
################################################################

Is there a standard message format for this sort of thing?  If it's
like the remailer ``standards'' that appears to be written by whomever
writes the code first.

I need a hook that gets called sometime after mc-decrypt and both
before and after the replace file on disk gets called.  The hook
probably needs to go into mc-toplev.el, although
gnus-summary-edit-done is a possibility too.  I'm not sure what can
reasonably be done with the header block at the bottom, though I know
I want the opportunity of being able to take them and replace the
bogus list supplied values with them.

The edit article sequence is confusing right now since the changes
made are not reflected in the *Summary* buffer.  This should probably
be fixed.

-- 
steve@miranova.com baur

Re: PGP Encrypted Mailing Lists (FYI)

[Stainless Steel Rat]

-----BEGIN PGP SIGNED MESSAGE-----

>>>>> "SLB" == Steven L Baur <steve@miranova.com> writes:

[...]

SLB> Is there a standard message format for this sort of thing?  If it's
SLB> like the remailer ``standards'' that appears to be written by
SLB> whomever writes the code first.

There is no such "standard" other than what might become a defacto
standard through common usage.  The only formatting standard PGP uses is
the various PEM block defintions.  This thing you have shown us is, IMO,
a real mess.

[...]

SLB> I'm not sure what can reasonably be done with the header block at
SLB> the bottom, though I know I want the opportunity of being able to
SLB> take them and replace the bogus list supplied values with them.

Write something for yourself and add it to mc-post-decryption-hook.

SLB> The edit article sequence is confusing right now since the changes
SLB> made are not reflected in the *Summary* buffer.  This should probably
SLB> be fixed.

That is probably a bug :).

From: ratinox@ccs.neu.edu To: ding@ifi.uio.no Message-ID:
srg2deyjii.fsf@delphi.ccs.neu.edu Date: 17 Jan 1996 09 37:41 -0500

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQCVAwUBMP0Jyp6VRH7BJMxHAQGeEQQAsuGQXYFltIa5ohV7Cp2Fb/ilr5EldiXH
uwTBU8qH+q4vjPzhtM0JUjVifdh1GlWxhm0BrYI+wZSlHeI0veHOTA6l8n9HWgaD
imAr6d4mSAA35AsFGdUqm4aN29iU/csSvAxQO5TinmUssfD+3qkXLQ/7H0giymwK
YhAa2KJRWSA=
=vckv
-----END PGP SIGNATURE-----
-- 
Rat <ratinox@ccs.neu.edu>          \ Warning: pregnant women, the elderly, and
PGP Public Key: Ask for one today!  \ children under 10 should avoid prolonged
http://www.ccs.neu.edu/home/ratinox/ \ exposure to Happy Fun Ball.

Re: PGP Encrypted Mailing Lists (FYI)

[Lars Magne Ingebrigtsen]

Steven L Baur <steve@miranova.com> writes:

> The edit article sequence is confusing right now since the changes
> made are not reflected in the *Summary* buffer.  

Actually, September 0.27 does that.  It doesn't work, though.  Fix in
0.28.  However, `gnus-summary-edit-article-postpone' doesn't update
the summary buffer...  Should it?

-- 
Home is where the cat is.