1994-03-01 - Re: your mail

Header Data

From: Jeremy Cooper <jeremy@crl.com>
To: N/A
Message Hash: aabf668b19efec91bc9e073c5a0c7555d07e439b33ae9c81fc3f71381117d7a8
Message ID: <Pine.3.87.9402282107.A19923-0100000@crl.crl.com>
Reply To: <9402281807.AA18357@glia.biostr.washington.edu>
UTC Datetime: 1994-03-01 05:06:14 UTC
Raw Date: Mon, 28 Feb 94 21:06:14 PST

Raw message

From: Jeremy Cooper <jeremy@crl.com>
Date: Mon, 28 Feb 94 21:06:14 PST
Subject: Re: your mail
In-Reply-To: <9402281807.AA18357@glia.biostr.washington.edu>
Message-ID: <Pine.3.87.9402282107.A19923-0100000@crl.crl.com>
MIME-Version: 1.0
Content-Type: text/plain


On Mon, 28 Feb 1994 cowen@glia.biostr.washington.edu wrote:

>  also a few comments.
>  
>  once in place, i could do several things to make it hard to catch me
>  i could write everything i send out in a seperate code, only send snail
>  mail, only talk in person, steal the code keys, take the chip out of all
>  the systems i have access to. and lets see, i could tell you i have a chip
>  that looks liek the clipper chip, that on the first test try works.
>  but it is really a fake, and mass produce it and sell it. without your knowing
>  hey anything is possible.
>

Now why bother going through all the trouble to take out the chip?  Why 
not just leave it in there and send RSA encrypted over your phone line?  
Once they _DO_ decrypt your clipper, they will still have another 
barrier.  Leaving the chip in there does make it a little harder even for 
law enforcement doesn't it? 

                   _  .  _ ___ _  .  _
===-|)/\\/|V|/\/\ (_)/_\|_|\_/(_)/_\|_| Stop by for an excursion into the-===
===-|)||| | |\/\/  mud.crl.com 8888 (_) Virtual Bay Area!                -===







Thread