1994-07-06 - entropy of data….?

Header Data

From: “Claborne, Chris at SanDiegoCA” <claborne@microcosm.sandiegoca.NCR.COM>
To: cypherpunks <cypherpunks@toad.com>
Message Hash: 292c522a1490785a93f74230cd59cbc6878de42c24ac56f282d0a73f800c9364
Message ID: <2E1B3A56@microcosm.SanDiegoCA.NCR.COM>
Reply To: N/A
UTC Datetime: 1994-07-06 23:49:55 UTC
Raw Date: Wed, 6 Jul 94 16:49:55 PDT

Raw message

From: "Claborne, Chris at SanDiegoCA" <claborne@microcosm.sandiegoca.NCR.COM>
Date: Wed, 6 Jul 94 16:49:55 PDT
To: cypherpunks <cypherpunks@toad.com>
Subject: entropy of data....?
Message-ID: <2E1B3A56@microcosm.SanDiegoCA.NCR.COM>
MIME-Version: 1.0
Content-Type: text/plain




 ----------
From: Jeff Gostin<jgostin@eternal.pha.pa.us>
> can't be broken in a reasonable amount of time. I'm  interested in what
> most of the people on this list would consider a reasonable amount of
> time though.

Hasn't someone come up with a name for this like "Entropy of the data is 30 
days" or... "the half-life of the data is 15 days".  This is a critical 
value when looking at it from a military point of view.  If you can't decode 
enemy plan for attack before a certain date/time then the info is 
useless....

     2
 -- C  --
                                        ...  __o
                                       ..   -\<,
chris.claborne@sandiegoca.ncr.com      ...(*)/(*).          CI$: 76340.2422
PGP Pub Key fingerprint =  A8 FA 55 92 23 20 72 69  52 AB 64 CC C7 D9 4F CA
Avail on Pub Key server.





Thread