1995-09-06 - Re: Another Son of Clipper discussion paper

Header Data

From: Deranged Mutant <rrothenb@ic.sunysb.edu>
To: jim@rand.org (Jim Gillogly)
Message Hash: 964efcbb8560a1bffc928bcd10981ea31237761bef0f71d16c6e8d11ae0f4d6f
Message ID: <199509060858.EAA15990@libws4.ic.sunysb.edu>
Reply To: <199509052053.NAA01226@mycroft.rand.org>
UTC Datetime: 1995-09-06 08:57:46 UTC
Raw Date: Wed, 6 Sep 95 01:57:46 PDT

Raw message

From: Deranged Mutant <rrothenb@ic.sunysb.edu>
Date: Wed, 6 Sep 95 01:57:46 PDT
To: jim@rand.org (Jim Gillogly)
Subject: Re: Another Son of Clipper discussion paper
In-Reply-To: <199509052053.NAA01226@mycroft.rand.org>
Message-ID: <199509060858.EAA15990@libws4.ic.sunysb.edu>
MIME-Version: 1.0
Content-Type: text/plain



> 
> Key Escrow Issues Meeting, September 6-7, 1995
> Discussion Paper #3
> 
>                  Export Criteria Discussion Draft --
>                 64-bit Software Key Escrow Encryption

Pardon my obvious question, but if there's some sort of GAK/LEAF, then
why limit it to 64-bit? It seems possible that the assumption is 'just
in case the GAK is tampered with' there's still a chance of cracking it,
should the need arise.

[..]

I'm wondering just how securely a hack-proof escrow system can be written.
It seems that someone can always go in with a sophisticated debugger and
do some tampering of the software.

And one need not mention the what-if-foreign-competitors-do-not-implement-
this-scheme? question...





Thread