1994-03-19 - Re: CLIPPER COMPROMIZED?

Header Data

From: sommerfeld@orchard.medford.ma.us (Bill Sommerfeld)
To: mech@eff.org
Message Hash: ef524ded51476595790d64566238caa9d53590047d5b6eb55823cea4037885e2
Message ID: <199403190253.VAA00379@orchard.medford.ma.us>
Reply To: <199403181924.OAA15439@eff.org>
UTC Datetime: 1994-03-19 03:05:41 UTC
Raw Date: Fri, 18 Mar 94 19:05:41 PST

Raw message

From: sommerfeld@orchard.medford.ma.us (Bill Sommerfeld)
Date: Fri, 18 Mar 94 19:05:41 PST
To: mech@eff.org
Subject: Re: CLIPPER COMPROMIZED?
In-Reply-To: <199403181924.OAA15439@eff.org>
Message-ID: <199403190253.VAA00379@orchard.medford.ma.us>
MIME-Version: 1.0
Content-Type: text/plain


Ok, so we have a wire service report citing unnamed sources that the
gov't is trying to find out if Ames could have had access to Clipper,
and Denning citing unnamed sources that Ames probably didn't have
access to Clipper...

IMHO, that's roughly a tie in the credibility race, especially given
Denning's known biases on the matter.

At this stage in the clipper deployment, it would not be hard for them
to "recall" all the outstanding clipper/capstone/etc. chips for an,
umm, "bug fix", which installed a new set of S-boxes & a new family
key.

In any event, anyone who had compromised clipper would be a fool to
show his hand now.. it would make a lot more sense to wait until
deployment was seriously under way, and clipperphones had gotten into
the hands (& electron microscopes :-) ) of at least some anti-clipper
activists... that way, it would be impossible for the gov't to dismiss
such a compromise as a hoax.

					- Bill

















Thread