1994-03-02 - Re: Insecurity of public key crypto #1 (reply to Mandl)

Header Data

From: “Perry E. Metzger” <pmetzger@lehman.com>
To: Eric Johnson <ejohnson@pmip.dist.maricopa.edu>
Message Hash: 36737ea949485430988ce3c215ac03ae68fa963ac13af4404c1525c2d774bf31
Message ID: <9403021214.AA21553@andria.lehman.com>
Reply To: <199403020511.WAA21677@pmip.dist.maricopa.edu>
UTC Datetime: 1994-03-02 12:15:29 UTC
Raw Date: Wed, 2 Mar 94 04:15:29 PST

Raw message

From: "Perry E. Metzger" <pmetzger@lehman.com>
Date: Wed, 2 Mar 94 04:15:29 PST
To: Eric Johnson <ejohnson@pmip.dist.maricopa.edu>
Subject: Re: Insecurity of public key crypto #1 (reply to Mandl)
In-Reply-To: <199403020511.WAA21677@pmip.dist.maricopa.edu>
Message-ID: <9403021214.AA21553@andria.lehman.com>
MIME-Version: 1.0
Content-Type: text/plain



Eric Johnson says:
> : Please don't do that.  I don't want to go through hoops to read this
> : mailing list.  It's already cumbersome as is.  Adding PGP in the soup
> : would make things very nasty.  I'd rather not use PGP except for private
> : messages.
> 
> That was exactly the point Eric Hughes was making; it is not a good
> strategy to save encryption for only private communications.
> 
> Besides, procmail (or similar) should be able to handle piping
> incoming cypherpunks traffic through the decryptor, so the hoop 
> would be transparent anyway.  No muss, no fuss.

So, will procmail run for someone getting this mailing list via CCMail
under DOS? There are people doing that, you know.

Its one thing to write tools so people can encrypt their routine
PRIVATE mail. Its another thing to encrypt mailing lists read by
hundreds of people. The former can be adjusted on a case by case basis
-- the latter cannot.

Perry





Thread