1994-01-27 - Re: clipper pin-compatible chip

Header Data

From: drzaphod@brewmeister.xstablu.com (DrZaphod)
To: koontzd@lrcs.loral.com (David Koontz)
Message Hash: 9617db836e86e64a94381c99a59addf55e20ce533180dcd71d60f8893742c6d9
Message ID: <m0pPPCs-0003DXC@brewmeister.xstablu.com>
Reply To: <9401261919.AA22973@io.lrcs.loral.com>
UTC Datetime: 1994-01-27 05:27:28 UTC
Raw Date: Wed, 26 Jan 94 21:27:28 PST

Raw message

From: drzaphod@brewmeister.xstablu.com (DrZaphod)
Date: Wed, 26 Jan 94 21:27:28 PST
To: koontzd@lrcs.loral.com (David Koontz)
Subject: Re: clipper pin-compatible chip
In-Reply-To: <9401261919.AA22973@io.lrcs.loral.com>
Message-ID: <m0pPPCs-0003DXC@brewmeister.xstablu.com>
MIME-Version: 1.0
Content-Type: text/plain


> Operating in a system expecting a clipper chip potentially restricts
> the keyspace.  Non-centrally selected keys use the clipper chip to
> 'fish' for the CCW, where it is re-fed.  The host system (to the 
> clipper chip) is going to try and feed 10 bytes plush 3 bytes of
> a constant.  Utilizing IDEA, the key is supposed to be 16 Bytes.
> 
> The point being that dropping an IDEA chip in is not 'plug and play'.

	Couldn't one compress the IDEA key to 10 bytes and 3?  The
hardware wouldn't notice and since you'd be using an IDEA chip on
both sides it could decompress and verify on the other end.

-- 
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
- DrZaphod                #Don't Come Any Closer Or I'll Encrypt!   -
- [AC/DC] / [DnA][HP]     #Xcitement thru Technology and Creativity -
- [drzaphod@brewmeister.xstablu.com] [MindPolice Censored This Bit] -
-         50 19 1C F3 5F 34 53 B7   B9 BB 7A 40 37 67 09 5B         -
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-




Thread