1996-10-03 - Re: How might new GAK be enforced?

Header Data

From: jonathon <grafolog@netcom.com>
To: Steve Schear <azur@netcom.com>
Message Hash: 5e37f11a55a2aa884f8aa8f8ea9cf94dc5b3fc44f4adbae77267c10d19bd1235
Message ID: <Pine.SUN.3.95.961003045215.14505G-100000@netcom7>
Reply To: <v02130503ae781347afee@[10.0.2.15]>
UTC Datetime: 1996-10-03 12:26:42 UTC
Raw Date: Thu, 3 Oct 1996 20:26:42 +0800

Raw message

From: jonathon <grafolog@netcom.com>
Date: Thu, 3 Oct 1996 20:26:42 +0800
To: Steve Schear <azur@netcom.com>
Subject: Re: How might new GAK be enforced?
In-Reply-To: <v02130503ae781347afee@[10.0.2.15]>
Message-ID: <Pine.SUN.3.95.961003045215.14505G-100000@netcom7>
MIME-Version: 1.0
Content-Type: text/plain


On Wed, 2 Oct 1996, Steve Schear wrote:

> Another possible monkey wrench is to send non-GAK messages containg random
> data.  Since the entropy of encrypted and RNG data should be identical you

	Send things like the contents of  alt.binary.pictures.something
	only use every other line of the encoded material in them.

	Intersperse that with your normal e-mail, and never have
	headers for anything.    

	And lets not forget that alt.binary.pictures.something is a
	great place to send/recieve encrypted messages that 99.99%
	of the viewers won't realize are encrypted messages.







Thread