As a fork bomb’s mode of operation is entirely dependent on being able to create new processes, one way of preventing a fork bomb from severely affecting the entire system is to limit the maximum number of processes that a single user may own. For such a simple script, each individual iteration would hardly take a few milliseconds, so the first few iterations complete very quickly and soon it becomes more than what the computer can handle.Īny antivirus worth it’s salt would be able to scan this suspicious executable file and warn the user before execution.
The first instance will likely not even complete 50 iterations before the system grinds to a halt and crashes. After 100 iterations we have 2100 = 1.267 nonillion, a number so big you don’t even know what ‘nonillion’ is (It’s 1030). After 10 iterations we have 1024 (210) instances of our little batch file. After another cycle, each of those two create another two for a total of four (22). After one iteration of the loop, two programs (21) are created. So every time the loop is run another instance of the same program is started and then both of them run together and again duplicate themselves and so on.Įvery program doubling itself is a form of exponential growth.
By start %0 we’re running the same file again.Īnd finally goto s brings us back to the top, forming a loop. %0 actually refers to the name of the batch file itself.
0 kommentar(er)
