Search results
Results from the WOW.Com Content Network
The concept behind a fork bomb — the processes continually replicate themselves, potentially causing a denial of service. In computing, a fork bomb (also called rabbit virus) is a denial-of-service (DoS) attack wherein a process continually replicates itself to deplete available system resources, slowing down or crashing the system due to resource starvation.
The problem was first reported as early as 2002, [3] but began to be widely addressed in 2008. [4] Defenses against this kind of attack include capping the memory allocated in an individual parser if loss of the document is acceptable, or treating entities symbolically and expanding them lazily only when (and to the extent) their content is to ...
The Rabbit (or Wabbit) virus, more a fork bomb than a virus, is written. The Rabbit virus makes multiple copies of itself on a single computer (and was named " rabbit " for the speed at which it did so) until it clogs the system, reducing system performance, before finally reaching a threshold and crashing the computer.
Article mentions that bash fork bomb was created by Jaromil in 2002. I was able to find posts of a polish white hat - lcamtuf from 1999 in usenet, in which he had this fork bomb in his signature. Necc 17:25, 13 March 2008 (UTC) If you can cite a source of this update the page ;) You might want to tell Jaromil too!
One of the earliest references to a fork concept appeared in A Multiprocessor System Design by Melvin Conway, published in 1962. [1] Conway's paper motivated the implementation by L. Peter Deutsch of fork in the GENIE time-sharing system, where the concept was borrowed by Ken Thompson for its earliest appearance [2] in Research Unix.
David A. Wheeler notes [9] four possible outcomes of a fork, with examples: The death of the fork. This is by far the most common case. It is easy to declare a fork, but considerable effort to continue independent development and support. A re-merging of the fork (e.g., egcs becoming "blessed" as the new version of GNU Compiler Collection.)
This had the same effect as a fork bomb, and crashed the computer several times. The main body of the worm can infect only DEC VAX machines running 4 BSD , alongside Sun-3 systems. A portable C "grappling hook" component of the worm was used to download the main body parts, and the grappling hook runs on other systems, loading them down and ...
The first use of a time bomb in software may have been in 1979 with the Scribe markup language and word processing system, developed by Brian Reid.Reid sold Scribe to a software company called Unilogic (later renamed Scribe Systems [2]), and agreed to insert a set of time-dependent functions (called "time bombs") that would deactivate freely copied versions of the program after a 90-day ...