The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Ken Thompson <kenbob@gmail.com>
To: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>
Cc: TUHS main list <tuhs@tuhs.org>
Subject: [TUHS] Re: early unix rand
Date: Tue, 12 Mar 2024 09:32:30 -0700	[thread overview]
Message-ID: <CAMP=X_nn5aSAFT+8S4-W2LU5urPkwC_JoDJhdhPBDzP3RFchgQ@mail.gmail.com> (raw)
In-Reply-To: <CAKH6PiXnww2bvj_Y0AGfq+rHdfhK3aLo01Mzb2mAc7AQ+R6TGg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1682 bytes --]

i wrote the generator.
dmr or rhm wrote the comment.
it came about after one of the first
drafts of a graphical pool game.
the balls were points and the test
was the bouncing off the edge of
the pool table. the balls were placed
at "random" places on the table,
they were started with "random"
directions and "random" velocities.
frictionless it ran forever.

after many minutes, from a mess
of dots, they form a line, later a couple
lines, later several points, and finally
after a large fraction of an hour, all the
balls would converge on a single dot.

that version of the program was saved
with the name "wierd" (spelling on purpose).
i have no idea if it exists now.


On Tue, Mar 12, 2024 at 7:38 AM Douglas McIlroy <
douglas.mcilroy@dartmouth.edu> wrote:

>  > The author of this routine has been writing
> >   random-number generators for many years and has
> >   never been known to write one that worked.
>
> It sounds like Ken to me. Although everybody had his
> own favorite congruential random number generator,
> some worse than others, I believe it was Ken who put
> one in the math library.
>
> The very fact that rand existed, regardless of its quality,
> enabled a lovely exploit. When Ken pioneered password
> cracking by trying every word in word lists at hand, one
> of the password files he found plenty of hits in came from
> Berkeley. He told them and they responded by assigning
> random passwords to everybody. That was a memorable
> error. Guessing that the passwords were generated by
> a simple encoding of the output of rand, Ken promptly
> broke 100% of the newly "hardened" password file.
>
> Doug
>

[-- Attachment #2: Type: text/html, Size: 2440 bytes --]

  parent reply	other threads:[~2024-03-12 16:32 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-12 14:37 [TUHS] " Douglas McIlroy
2024-03-12 16:23 ` [TUHS] " Paul Winalski
2024-03-12 16:47   ` [TUHS] Re: NSFW passwords William Cheswick
2024-03-13  1:22   ` [TUHS] Re: early unix rand Russ Cox
2024-03-12 16:32 ` Ken Thompson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-03-12 12:55 [TUHS] " Russ Cox
2024-03-12 18:08 ` [TUHS] " Russ Cox
2024-03-12 23:05 ` Jonathan Gray
2024-03-13  1:09   ` ron minnich
2024-03-13 16:41     ` ron minnich
2024-03-13 17:17       ` ron minnich
2024-03-13 20:25         ` Rob Pike
2024-03-13 20:34           ` Clem Cole
2024-03-14 19:24             ` Dave Horsfall

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMP=X_nn5aSAFT+8S4-W2LU5urPkwC_JoDJhdhPBDzP3RFchgQ@mail.gmail.com' \
    --to=kenbob@gmail.com \
    --cc=douglas.mcilroy@dartmouth.edu \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).