cryptoanarchy.wiki

Arise, you have nothing to lose but your barbed wire fences!

1993-01-05 - purloined letter

Header Data

From: Peter Breton <pbreton@cs.umb.edu>
To: cypherpunks@toad.com
Message Hash: ace15c040f6143786e8c23629edafaae36d3024fe3329829b17f9df8c17cb662
Message ID: <Pine.3.03.9301051003.C13150-9100000@ra.cs.umb.edu>
Reply To: <9301050049.AA07963@parallax.com>
UTC Datetime: 1993-01-05 15:26:50 UTC
Raw Date: Tue, 5 Jan 93 07:26:50 PST

Raw message

From: Peter Breton <pbreton@cs.umb.edu>
Date: Tue, 5 Jan 93 07:26:50 PST
To: cypherpunks@toad.com
Subject: purloined letter
In-Reply-To: <9301050049.AA07963@parallax.com>
Message-ID: <Pine.3.03.9301051003.C13150-9100000@ra.cs.umb.edu>
MIME-Version: 1.0
Content-Type: text/plain



  Hi,

  I'm fairly new here and not sure if this topic has come up before, but
I'll offer it anyway:

 In using encrypted communications, how does one avoid the problem of
calling attention to the message BECAUSE it is encrypted? "If he went to
the trouble of coding it, there MUST be something in there!!" Granted that
if everyone begins encrypting, this problem will vanish... are there
practical solutions in the meantime? (eg, Codes that look like plaintext?)
	
	
		Peter

Thread