1993-09-29 - Re: Clipper specifics

Header Data

From: Eli Brandt <ebrandt@jarthur.Claremont.EDU>
To: cypherpunks@toad.com
Message Hash: 7f885727667b85267a20afcd68dfe409f98bd73e0c8bc9cec8205de362152ba7
Message ID: <9309290733.AA19505@toad.com>
Reply To: <9309290546.AA27506@longs.lance.colostate.edu>
UTC Datetime: 1993-09-29 07:36:22 UTC
Raw Date: Wed, 29 Sep 93 00:36:22 PDT

Raw message

From: Eli Brandt <ebrandt@jarthur.Claremont.EDU>
Date: Wed, 29 Sep 93 00:36:22 PDT
To: cypherpunks@toad.com
Subject: Re: Clipper specifics
In-Reply-To: <9309290546.AA27506@longs.lance.colostate.edu>
Message-ID: <9309290733.AA19505@toad.com>
MIME-Version: 1.0
Content-Type: text/plain


> From: "L. Detweiler" <ld231782@longs.lance.colostate.edu>
> *create* the field), and it is handled outside the chip, there is no
> guarantee that the system designer does not, for example, encrypt the
> LEEF in the communications transit, thereby completely sabotaging the
> `exploitative' tappability of the chip.
> 
> Hence there is a *very* real possibility that this scheme, or something
> similar, could be used to gain Skipjack-level encryption without any
> key escrow complications. I suspect the NSA is *extremely* worried
> about this.

Their spokesagency, NIST, has said that it will be illegal to encrypt
on top of Skipjack or to mung the LEEF.  Pre-encryption is not
mentioned, AFAIK, and would be borderline impossible to detect anyway.  

As I see it, this is already a restriction on non-Skipjack encryption,
issued in the same document that assured us that no such thing is being
considered.  It's a special case, to be sure, but it clearly asserts a
government power to restrict the means and manner of private
encryption performed entirely within the United States.  This is a key
issue, IMO.

   Eli   ebrandt@jarthur.claremont.edu





Thread