The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: fair-tuhs@netbsd.org (Erik E. Fair)
Subject: [TUHS] Happy birthday, Morris Worm!
Date: Wed, 15 Nov 2017 17:05:34 -0800	[thread overview]
Message-ID: <2270.1510794334@cesium.clock.org> (raw)
In-Reply-To: <003701d35e5c$493a0e20$dbae2a60$@ronnatalie.com>

Unless I'm mistaken, the Morris worm was the first such incident to make the front page of the New York Times (in an article by now-retired John Markoff):

http://www.nytimes.com/1988/11/04/us/virus-in-military-computers-disrupts-systems-nationwide.html

So I'm not surprised that other reporters started poking around. No one thought to call Apple (at least, not that anyone told me about), but given the limited nature (and understanding) of the Internet at the time, and its characterization by Markoff as "military", this is not too surprising. My group was a little worried about an AppleTalk-based virus getting loose in the Apple Engineering Network ... and that sort-of did happen, not very long after:

http://virus.wikidot.com/wdef

Fortunately, WDEF had a bug which limited its spread to promiscuous media exchange (floppies) - AppleShare volumes didn't have the resource it attempted to infect (a "desktop database"), and thus if your computer had WDEF, the first attempt to mount an AppleShare volume would crash your system - at that time, most Macs didn't have MMUs and didn't run real operating systems like Unix ... and we inside Apple used AppleShare extensively. Also easy to clean out: just rebuild the "desktop database" (hold down Option key when mounting disk volumes, IIRC).

I'm also pretty sure that the Morris worm was the impetus for the formation of the Computer Emergency Response Team (CERT) at CMU Software Engineering Institute (SEI):

https://en.wikipedia.org/wiki/Computer_emergency_response_team

It looks like Wikipedia agrees with me.

Tom Duff gave a related talk & paper at Summer USENIX 1989 that was most
interesting, "Experience with Viruses on UNIX Systems":

https://www.usenix.org/legacy/publications/compsystems/1989/spr_duff.pdf

I especially liked the bit in which Tom's virus infected a multi-level secured UNIX system that Doug McIlroy and Jim Reeds were developing which they didn't spot until they turned on all their protections ... and programs started crashing all over the place.

	Erik


  reply	other threads:[~2017-11-16  1:05 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-01 22:17 Dave Horsfall
2017-11-01 22:32 ` Lyndon Nerenberg
2017-11-02 16:43   ` Don Hopkins
2017-11-01 23:03 ` Charles H. Sauer
2017-11-01 23:15 ` Paul Winalski
2017-11-02  0:06 ` Ralph Corderoy
2017-11-02  0:09 ` Dan Cross
2017-11-02  1:08   ` Clem cole
2017-11-02  8:18 ` arnold
2017-11-02 17:56 ` Don Hopkins
2017-11-02 18:32   ` Lars Brinkhoff
2017-11-02 20:32     ` Don Hopkins
2017-11-02 21:59       ` Don Hopkins
2017-11-02 22:27         ` Ralph Corderoy
2017-11-04  1:15 ` Dave Horsfall
2017-11-15 21:36   ` Erik E. Fair
2017-11-15 21:50     ` Don Hopkins
2017-11-15 21:54     ` Ron Natalie
2017-11-16  1:05       ` Erik E. Fair [this message]
2017-11-16  1:22     ` Will Senn
2017-11-16  1:56       ` Erik E. Fair
2017-11-16  2:41         ` Ron Natalie
2017-11-16  3:00         ` Don Hopkins
2017-11-16  7:39         ` Steve Simon
2017-11-16 15:54         ` Clem Cole
2017-11-16 15:58           ` Jon Steinhart
2017-11-02  3:46 Doug McIlroy
2017-11-02  5:53 ` George Michaelson
2017-11-02 12:10 Noel Chiappa
2017-11-02 14:26 ` Dan Cross
2017-11-02 13:46 Norman Wilson
2017-11-02 14:32 ` Chet Ramey
2017-11-02 14:42 ` Will Senn
2017-11-02 15:00   ` Michael Kjörling
2017-11-02 15:26     ` Tim Bradshaw
2017-11-02 16:48       ` Don Hopkins
2017-11-02 16:50       ` Don Hopkins
2017-11-02 16:52       ` Don Hopkins
2017-11-02 16:54       ` Don Hopkins
2017-11-02 16:56       ` Don Hopkins
2017-11-02 16:57       ` Don Hopkins
2017-11-02 17:00       ` Don Hopkins
2017-11-02 17:57         ` Don Hopkins
2017-11-02 15:25   ` Dan Cross
2017-11-02 15:52     ` Will Senn
2017-11-02 18:42     ` Ken Thompson
2017-11-03  0:53 Doug McIlroy
2017-11-03  1:39 ` Ken Thompson
2017-11-03  9:25   ` arnold
2017-11-03 10:23 Noel Chiappa
2017-11-03 11:20 ` arnold
2017-11-03 13:11 ` Arthur Krewat
2017-11-03 19:26   ` Toby Thain
2017-11-03 20:54     ` Arthur Krewat
2017-11-16 23:24 Doug McIlroy
2017-11-16 23:35 ` Ralph Corderoy
2019-11-01 20:36 Dave Horsfall
2019-11-01 21:12 ` Dan Cross
2019-11-01 21:49 ` A. P. Garcia
2019-11-02  6:35   ` William Corcoran
2019-11-02  6:44     ` William Corcoran
2019-11-02  7:31       ` A. P. Garcia

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=2270.1510794334@cesium.clock.org \
    --to=fair-tuhs@netbsd.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).