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

Header Data

From: Eric Johnson <ejohnson@pmip.dist.maricopa.edu>
To: hughes@ah.com
Message Hash: c991510d1ce83db914c51df966dc8cf77bf11c6acdee2c4aa8bb30da36ea51c8
Message ID: <199403020015.RAA21139@pmip.dist.maricopa.edu>
Reply To: N/A
UTC Datetime: 1994-03-02 00:20:24 UTC
Raw Date: Tue, 1 Mar 94 16:20:24 PST

Raw message

From: Eric Johnson <ejohnson@pmip.dist.maricopa.edu>
Date: Tue, 1 Mar 94 16:20:24 PST
To: hughes@ah.com
Subject: Re: Insecurity of public key crypto #1 (reply to Mandl)
Message-ID: <199403020015.RAA21139@pmip.dist.maricopa.edu>
MIME-Version: 1.0
Content-Type: text/plain


: >Only "sensitive" information is worth encrypting and if you want to
: >stay out of trouble you don't go giving sensitive information to
: >someone you don't know.  
:
: If part of your communications are encrypted and part are not you have
: sent the message about what information is sensitive and what is not.
: This difference in encoding is a fir-class message in it's own right.
:
: Therefore _all_ communications should be encrypted at all time.  It is
: no argument against the principle that this is difficult to do at the
: current time.
:
: Eric
:

Would it not make sense, therefore, to publish a public cypherpunks
mailing list key, which is returned with subscription requests?
All incoming message cleartext to the mailing list server would
then be encrypted in the server's key; not for security, but 
precisely for the reason you state above.  That _would_ create
quite a volume of encrypted communications to each receipient of 
the list.

	--Eric





Thread