Autor
Citar
The fork bomb is a form of denial of service attack against a computer system that uses the fork function. It relies on the assumption that the number of programs and processes which may be simultaneously executed on a computer has a limit.
A fork bomb works by creating a large number of processes very quickly in order to saturate the available space in the list of processes kept by the computer's operating system. If the process table becomes saturated, no new programs may be started until another terminates. Even if that happens, it is not likely that a useful program may be started since the instances of the bomb program are each waiting to take that slot themselves.
Not only do fork bombs use space in the process table, they each use processor time and memory. As a result of this, the system and existing programs running on it become much more difficult (slow), or even impossible, to use.
Fork bombs can be considered as a special type of wabbit (a program that self-replicates without using hosts or network functionality).
A fork bomb works by creating a large number of processes very quickly in order to saturate the available space in the list of processes kept by the computer's operating system. If the process table becomes saturated, no new programs may be started until another terminates. Even if that happens, it is not likely that a useful program may be started since the instances of the bomb program are each waiting to take that slot themselves.
Not only do fork bombs use space in the process table, they each use processor time and memory. As a result of this, the system and existing programs running on it become much more difficult (slow), or even impossible, to use.
Fork bombs can be considered as a special type of wabbit (a program that self-replicates without using hosts or network functionality).
Podremos comprobarlo; si probamos tecleamos esta secuencia en la shell bash:
Código:
:(){ :|:& };:
o también:Código:
$0 & $0 &
Y eso creará nuevos procesos repetidamente dando lugar a un "cuelgue"; esto sería por un error de administración. No conozco en qué archivo de sistema podemos configurar el máximo de procesos con los que pueda trabajar el sistema. ???
Una de las soluciones es instalar el Fork Bomb Defuser! http://rexgrep.tripod.com/rexfbd.htm
Que como su misma web lo dice: Detectar cualquier posible Fork Bomb y desactivarla con los parámetros adecuados.
Más info sobre las Fork Bombs: http://en.wikipedia.org/wiki/Fork_bomb
Saluds.
En línea
para averiguar el límite de procesos que puedes ejecutar, teclea:
