Earlier quoted context omitted.
A quick search shows: - a github repo containing "the original, de-compiled source code for the Morris Worm" - see https://github.com/agiacalone/morris-worm-malware - a high level report about the worm - see https://www.ee.torontomu.ca/~elf/hack/internet-worm.html
Both of those agree that is was '88...
This week in 1988, Robert Morris unleashed his eponymous worm
51–60 of 200 posts
Re: This week in 1988, Robert Morris unleashed his eponymous worm
#52>However, the pioneering Morris worm malware wasn’t made with malice, says an FBI retrospective on the “programming error.” It was designed to gauge the size of the Internet, resulting in a classic case of unintended consequences. had RTM actually RTM the world might be a bit different than it is today.
He did do us all a service; people back then didn't seem to realize that buffer overflows were a security risk. The model people had then, including my old boss at one of my first jobs in the early 80s, is that if you fed a program invalid input and it crashed, this was your fault because the program had a specification or documentation and you didn't comply with it.
Re: This week in 1988, Robert Morris unleashed his eponymous worm
#53I remember that the Boston Museum of Science used to have a floppy disk on display with the Morris worm on it.
Re: This week in 1988, Robert Morris unleashed his eponymous worm
#54Re: This week in 1988, Robert Morris unleashed his eponymous worm
#55[flagged]
Re: This week in 1988, Robert Morris unleashed his eponymous worm
#56Re: This week in 1988, Robert Morris unleashed his eponymous worm
#57That was one scary exciting day (source: was running machines at MIT at the time)
Re: This week in 1988, Robert Morris unleashed his eponymous worm
#58>However, the pioneering Morris worm malware wasn’t made with malice, says an FBI retrospective on the “programming error.” It was designed to gauge the size of the Internet, resulting in a classic case of unintended consequences. had RTM actually RTM the world might be a bit different than it is today.
Well, sort of. RTM underestimated the effect of exponential growth, and thought that he would in effect have an account on all of the connected systems, without permission. He evidently didn't intend to use this power for evil, just to see if it could be done. He did do us all a service; people back then didn't seem to realize that buffer overflows were a security risk. The model people had then, including my old bos…
It was Thomas Lopatic and 8lgm that really lit a fire under this (though likely they were inspired by Morris' work). Lopatic wrote the first public modern stack overflow exploit, for HPUX NCSA httpd, in 1995. Later that year, 8lgm teased (but didn't publish --- which was a big departure for them) a remote stack overflow in Sendmail 8.6.12 (it's important to understand what a big deal Sendmail vectors were at the time).
That 8lgm tease was what set Dave Goldsmith, Elias Levy, San Mehat, and Pieter Zatko (and presumably a bunch of other people I just don't know) off POC'ing the first wave of public stack overflow vulnerabilities. In the 9-18 months surrounding that work, you could look at basically any piece of privileged code, be it a remote service or an SUID binary or a kernel driver, and instantly spot overflows. It was the popularization with model exploits and articles like "Smashing The Stack" that really raised the alarm people took seriously.
That 7 year gap is really wild when you think about it, because during that time period, during which people jealously guarded fairly dumb bugs, like an errant pipe filter input to the calendar manager service that run by default on SunOS shelling out to commands, you could have owned up literally any system on the Internet, so prevalent were the bugs. And people blew them off!
I wrote a thread about this on Twitter back in the day, and Neil Woods from 8lgm responded... with the 8.6.12 exploit!
Re: This week in 1988, Robert Morris unleashed his eponymous worm
#59I find it funny that: 1) He released it from MIT to avoid suspicion. 2) After he was convicted, he went from Cornell to Harvard to complete his Ph.D. 3) He became an assistant professor at MIT after that. He had to be really spectacular/have crazy connections to still be able to finish his training at a top program and get a job at the institution he tried to frame.
Have you read any of his papers? Morris was not fucking around.
Re: This week in 1988, Robert Morris unleashed his eponymous worm
#60I find it funny that: 1) He released it from MIT to avoid suspicion. 2) After he was convicted, he went from Cornell to Harvard to complete his Ph.D. 3) He became an assistant professor at MIT after that. He had to be really spectacular/have crazy connections to still be able to finish his training at a top program and get a job at the institution he tried to frame.
Have you read any of his papers? Morris was not fucking around.
He was and is very smart. This is not disputed. He was 23 at the time. Not exactly a child.
The worm was surprisingly elaborate containing three separate remote exploits.
It probably took a few weeks to build and test.
So sabotaging thousands of at the time very expensive network connected computers was a very deliberate action.
I posit that he likely did it to become famous and perhaps even successful, feeling safe with his dad’s position. And it worked. He did not end up in prison. He ended up cofounding Viaweb and YCombinator.
Unironically a great role model for YC. :/