The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Doug McIlroy <doug@cs.dartmouth.edu>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Happy birthday Morris worm
Date: Sat, 2 Nov 2019 14:12:47 -0600	[thread overview]
Message-ID: <CANCZdfr1yiMbM6KixYgTXgWn5PVOQTtXWBhYODUjD_n1Lqq0Lg@mail.gmail.com> (raw)
In-Reply-To: <201911021412.xA2ECEMr137264@tahoe.cs.Dartmouth.EDU>

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

On Sat, Nov 2, 2019 at 8:13 AM Doug McIlroy <doug@cs.dartmouth.edu> wrote:

> Full disclosure: I served as a character witness at Robert Morris's trial.
> Before the trial, the judge was quite incredulous that the prosecutor
> was pursuing a felony charge and refused to let the trial go forward
> without confirmation from the prosecutor's superiors in Washington.
>
> > I'm sure that Bob was proud of his son's accomplishments -- but not
> that one.
>
> As Bob ut it, "It {being the father] is not a great career move."
> Robert confessed to Bob as soon as he realized the folly of loosing
> an exponential, even with a tiny growth rate per generation. I
> believe that what brought computers to their knees was the
> overwhelming number of attacks, not the cost of cecryption. The
> worm did assure that only one copy would be allowed to proceed
> at a time.
>
> During high school, Robert worked as a summer employee for Fred
> Grampp. He got high marks for finding and correcting an exploit.
>
> > making use of known vulnerabilities
>
> Buffer overflows were known to cause misbehavior, but few people
> at the time were conscious that the misbehavior could be controlled.
> I do not know whether Berkeley agonized before distributing the
> "debug" feature that allowed remote super-user access via sendmail.
> But they certainly messed up by not documenting it.
>

Yes. The reason people freaked out when the worm came out was because it
was the first one to hit the scene. The exploints that allowed it to
propagate were known to a few, but the notion of a self propagating thing
was quite novel (even if it had been theoretically discussed in many places
prior to the worm, and even though others had proven it via slower moving
vectors of BBS). It caught a lot of people off guard with their pants down,
and it took a bunch of time to rectify (because it would reinfect if you
weren't careful). That's why people wanted to prosecute on felony charges.
But there was no intent to cause harm, and there was, at the time, no
applicable law that could be used to charge as a felony anyway (apart from
vague denial of property statues, which were at best a stretch).

In hindsight people like to point at it and what a terrible thing it was,
but Robert just got there first. Any number of people could have written it
given the extremely lax security profiles of the time (things are better
today, but we are not immune to buffer overflows or privilege escalation
attacks).

Warner

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

  reply	other threads:[~2019-11-02 20:13 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-02 14:12 Doug McIlroy
2019-11-02 20:12 ` Warner Losh [this message]
2019-11-03 17:12   ` Paul Winalski
     [not found] <mailman.3.1572832803.30037.tuhs@minnie.tuhs.org>
2019-11-04 18:10 ` Paul McJones
2019-11-04 18:57   ` Bakul Shah
2019-11-04 19:24     ` Richard Salz
2019-11-05  3:48       ` Lawrence Stewart
2019-11-05 16:04         ` Ronald Natalie
2019-11-06 10:37           ` arnold
2019-11-06 13:35             ` Ronald Natalie
2019-11-04 19:25     ` SPC
2019-11-04 20:27     ` Dan Cross
2019-11-04 22:10       ` Michael Kjörling
2019-11-05  0:25     ` Anthony Martin
2019-11-12 20:56 Norman Wilson
2019-11-12 22:00 ` Dave Horsfall
2019-11-13  7:35 ` arnold
2019-11-12 22:24 Norman Wilson
2019-11-13 13:47 Doug McIlroy
2019-11-15 14:31 [TUHS] Happy birthday, " Doug McIlroy
2019-11-15 14:39 ` Warner Losh

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=CANCZdfr1yiMbM6KixYgTXgWn5PVOQTtXWBhYODUjD_n1Lqq0Lg@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=doug@cs.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).