Today's thread is just a quick pointer on a very well known command which you may have already heard of
This is called 'The Fork Bomb' - WARNING: DO NOT RUN THIS COMMAND UNLESS YOU ARE PREPARED FOR YOUR LINUX SYSTEM TO CRASH
The command of the Fork Bomb goes like this :(){ :|:& };:
This command will create a function that calls upon itself twice for every one call but doesn't have any stop command so it just keeps on repeating until the system runs out of memory and causes it to crash and require a reboot, the process would go on for an infinite amount of time if a machine could handle the memory hammering due to the fact that there is no end to the command but as we have not discovered how to accommodate for an infinite amount of memory your machine is guaranteed to crash due to this command so be careful, try running in a VM if you really want to see a live example!
Handy diagram showing the breakdown, pulled from an askubuntu source:
:(){ :|:& };:
\_/| |||| ||\- ... the function ':', initiating a chain-reaction: each ':' will start two more.
| | |||| |\- Definition ends now, to be able to run ...
| | |||| \- End of function-block
| | |||\- disown the functions (make them a background process), so that the children of a parent
| | ||| will not be killed when the parent gets auto-killed
| | ||\- ... another copy of the ':'-function, which has to be loaded into memory.
| | || So, ':|:' simply loads two copies of the function, whenever ':' is called
| | |\- ... and pipe its output to ...
| | \- Load a copy of the function ':' into memory ...
| \- Begin of function-definition
\- Define the function ':' without any parameters '()' as follows:
This is called 'The Fork Bomb' - WARNING: DO NOT RUN THIS COMMAND UNLESS YOU ARE PREPARED FOR YOUR LINUX SYSTEM TO CRASH
The command of the Fork Bomb goes like this :(){ :|:& };:
This command will create a function that calls upon itself twice for every one call but doesn't have any stop command so it just keeps on repeating until the system runs out of memory and causes it to crash and require a reboot, the process would go on for an infinite amount of time if a machine could handle the memory hammering due to the fact that there is no end to the command but as we have not discovered how to accommodate for an infinite amount of memory your machine is guaranteed to crash due to this command so be careful, try running in a VM if you really want to see a live example!
Handy diagram showing the breakdown, pulled from an askubuntu source:
:(){ :|:& };:
\_/| |||| ||\- ... the function ':', initiating a chain-reaction: each ':' will start two more.
| | |||| |\- Definition ends now, to be able to run ...
| | |||| \- End of function-block
| | |||\- disown the functions (make them a background process), so that the children of a parent
| | ||| will not be killed when the parent gets auto-killed
| | ||\- ... another copy of the ':'-function, which has to be loaded into memory.
| | || So, ':|:' simply loads two copies of the function, whenever ':' is called
| | |\- ... and pipe its output to ...
| | \- Load a copy of the function ':' into memory ...
| \- Begin of function-definition
\- Define the function ':' without any parameters '()' as follows:


![[Image: 4824998.gif]](https://hackhf.net/signature/4824998.gif)

![[Image: vibesignature.gif]](https://i.ibb.co/8LvxwtYQ/vibesignature.gif)