E. H. Spafford. The Internet Worm program: An analysis. Computer Communication Review, 19(1), Jan. 1989. Also issued as Purdue CS technical report TR-CSD-823. Home/Search Document Not in Database Summary Related Articles Check |
This paper is cited in the following contexts:
A Failure to Learn from the Past - Spafford (2003) Self-citation (Spafford) (Correct)
No context found.
E. H. Spafford. The Internet Worm program: An analysis. Computer Communication Review, 19(1), Jan. 1989. Also issued as Purdue CS technical report TR-CSD-823.
Computer Viruses as Artificial Life - Spafford (1994) (5 citations) Self-citation (Spafford) (Correct)
....The Xerox worms were actually useful they would travel from workstation to workstation, reclaiming file space, shutting off idle workstations, delivering mail, and doing other useful tasks. The Internet Worm of November 1988 is often cited as the canonical example of a damaging worm program. [26, 27, 22] The Worm clogged machines and networks as it spread out of control, replicating on thousands of machines around the Internet. Some authors (e.g. 7] labeled the Internet Worm as a virus, but those arguments are not convincing (cf. the discussion in [25] Most people working with ....
Eugene H. Spafford. The internet worm program: an analysis. Computer Communication Review, 19(1):17--57, January 1989. Also issued as Purdue CS technical report TR-CSD-823.
Software Forensics: Can We Track Code to its Authors? - Spafford, Weeber (1992) (5 citations) Self-citation (Spafford) (Correct)
....func(x) Each of these different source code segments exhibits features that could possibly be used in identifying the style of programming of an individual. These features may be lost to the examiner of the resultant executable code. For example, during the analysis of the Internet Worm program ([5, 15]) that remnant was reverse engineered to C programs that compiled to identical binary versions. In many cases, the analysts chose arbitrary names for variables and local subroutines the compiler would not save the values, so the choices did not matter. When the disassembled code was later ....
....long lists that were repeatedly searched. This was certainly a 1 Our experience with both undergraduate and graduate student programmers supports this supposition. poor approach, as the repeated searches of long lists dramatically reduced the efficiency of the program. This was noted in [15], and a correspondent later related that the Worm s author, Robert T. Morris, had been instructed in the Lisp programming language in his first undergraduate data structures and algorithms course. Although a coincidence such as this is certainly not sufficient upon which to base any specific ....
[Article contains additional citation context not shown here]
Eugene H. Spafford. The Internet worm program: an analysis. Computer Communication Review, 19(1), January 1989. Also issued as Purdue CS technical report TR-CSD-823.
Online articles have much greater impact More about CiteSeer.IST Add search form to your site Submit documents Feedback
CiteSeer.IST - Copyright Penn State and NEC