1994-06-03 - Re: Faster way to deescrow Clipper

Header Data

From: “Perry E. Metzger” <perry@imsi.com>
To: koontzd@lrcs.loral.com (David Koontz )
Message Hash: aff5f19479a74db2dae8491b90826926a6190e6bce4c541f8512f95d27c9ac9a
Message ID: <9406031840.AA04734@snark.imsi.com>
Reply To: <9406031829.AA19412@io.lrcs.loral.com>
UTC Datetime: 1994-06-03 18:40:42 UTC
Raw Date: Fri, 3 Jun 94 11:40:42 PDT

Raw message

From: "Perry E. Metzger" <perry@imsi.com>
Date: Fri, 3 Jun 94 11:40:42 PDT
To: koontzd@lrcs.loral.com (David Koontz )
Subject: Re: Faster way to deescrow Clipper
In-Reply-To: <9406031829.AA19412@io.lrcs.loral.com>
Message-ID: <9406031840.AA04734@snark.imsi.com>
MIME-Version: 1.0
Content-Type: text/plain



David Koontz says:
> I used to work on NSA cryptographic equipment.

So you've said. However,
1) If you had, anything interesting you could say would be classified,
   you'd have a clearance, and you'd go to jail for mentioning it.
2) you've shown every sign of being fairly clueless. 

I'll point out as an example the fact that you don't understand
initialization vectors, and this gem:
> If you have access to the control program (which you would if faking
> LEAFS),

Huh? Have you been paying attention? I have no idea what on earth the
"control program" is, but Matt's work certainly has nothing to do with
any such thing...

And this gem:

> The difficulty is
> that the DE (distant end) ain't necessarily smart enough to do so (assuming
> it has not been modified), and is more than likely looking for a passed data
> value (typically a sync symbol) to determine the state of crypto
> synchronization.

Ahem. What the hell are you talking about? Tessera has no concept of
"crypto synchronization" or the detection thereof.

.pm





Thread