1993-01-05 - Re: purloined letter

Header Data

From: mch@sqwest.wimsey.bc.ca (Mark C. Henderson)
To: Peter Breton <cypherpunks@toad.com
Message Hash: 906e5c65b825d6def3d457061bde6b1b347b2fd37841d01e2b9633a221e7f440
Message ID: <9301051019.ZM15222@west.sq.com>
Reply To: <Pine.3.03.9301051003.C13150-9100000@ra.cs.umb.edu>
UTC Datetime: 1993-01-05 18:27:47 UTC
Raw Date: Tue, 5 Jan 93 10:27:47 PST

Raw message

From: mch@sqwest.wimsey.bc.ca (Mark C. Henderson)
Date: Tue, 5 Jan 93 10:27:47 PST
To: Peter Breton <cypherpunks@toad.com
Subject: Re: purloined letter
In-Reply-To: <Pine.3.03.9301051003.C13150-9100000@ra.cs.umb.edu>
Message-ID: <9301051019.ZM15222@west.sq.com>
MIME-Version: 1.0
Content-Type: text/plain


On Jan 5, 10:19, Peter Breton wrote:
> Subject: purloined letter
> 
>   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?)
The best way to prevent this type of traffic analysis is to encrypt
everything. As a second best, encrypt all correspondence with a specific
person.

Mark

-- 
Mark Henderson, SoftQuad Inc, 108-10070 King George Hwy, Surrey, B.C. V3T 2W4
Internet:  markh@wimsey.bc.ca, mch@sqwest.wimsey.bc.ca, mch@holonet.net
UUCP: {van-bc,sq}!sqwest!mch Telephone: +1 604 585 8394  Fax: +1 604 585 1926
RIPEM public key available by Email/finger mch@holonet.net/keyserver





Thread