Article View: sci.crypt
Article #1861Re: pseudo one time pad...
From: Leonard Erickson
Date: Wed, 18 Nov 1992 13:26
Date: Wed, 18 Nov 1992 13:26
42 lines
2927 bytes
2927 bytes
lwloen@rchland.vnet.ibm.com (Larry Loen) writes: >The problem is, of course, random number generators designed to satisfy >statistical randomness may well not satisfy at all the need for being >unpredictable in a cryptographic situation; most are very poor at this, in >fact, not having been designed with the problem in mind. Most novices do >not understand the distinction between "randomness" as in passing Chi Square >and "unpredictable" as in frustrating analysis. So, they grab any old >random number generator out of Knuth or something and usually grab wrong. Well, one possibility is to point out that *by definition* there is *no* pattern to to digit stream that constitutes an irrational number, but the digit stream is *totally* predictable! So *statistically* the digits from an irrational (like pi or sqrt(2)) are random. But crypto folks would find them pretty useless. As a trivial example, I could send a message using PI as the key. But if you have any info about the message (say knowing that many messages from me start out in a certain way) you can try *assuming* that plaintext. Then when you see that the key comes out 314159 for the first part of the message, you may go "gee, that looks like Pi.." So you try plugging in the next few digits. If reasonable plaintext results, I'd be willing to bet you'd be looking for a table with Pi to a few hundred digits *fast*. I've *seen* a key get compromised this way (In a friendly environment). Someone saw that the plaintext messages between certain users allways had the same heading. So it was a reasonable assumption for the "enemy" to see what happened if he plugged in the heading and solved for the key. He never *did* figure out our key change schedule, but since this was only a battle of wits, we were only using a 20 digit key. So he could solve fotr the header and have a chunk of the message. Then he'd try to fill in the blanks per normal practice when you have a partial key. Now I know why lazy code clerks and standard message forms are so beloved of folks like the NSA! -- Leonard Erickson leonard@qiclab.scn.rain.com CIS: [70465,203] 70465.203@compuserve.com FIDO: 1:105/51 Leonard.Erickson@f51.n105.z1.fidonet.org (The CIS & Fido addresses are preferred)
Technical Details
Message-ID:
<1992Nov18.132658.23404@qiclab.scn.rain.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!uwm.edu!ogicse!qiclab!leonardReferences:
<1992Nov11.173642.29608@ee.eng.ohio-state.edu> <1992Nov11.193848.10946@rchland.ibm.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!haven.umd.edu!darwin.sura.net!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!uwm.edu!ogicse!qiclab!leonard From: leonard@qiclab.scn.rain.com (Leonard Erickson) Newsgroups: sci.crypt Subject: Re: pseudo one time pad... Message-ID: <1992Nov18.132658.23404@qiclab.scn.rain.com> Date: 18 Nov 92 13:26:58 GMT Article-I.D.: qiclab.1992Nov18.132658.23404 References: <1992Nov11.173642.29608@ee.eng.ohio-state.edu> <1992Nov11.193848.10946@rchland.ibm.com> Reply-To: Leonard.Erickson@f51.n105.z1.fidonet.org Organization: SCN Research/Qic Laboratories of Tigard, Oregon. Lines: 42