opens terminal, pauses So how fucked is my system gonna be afterwards?
If you’re referring to the cat, it’s a fork bomb. IIRC your system should realize what’s going on and terminate the process before your PC commits seppuku, unless your system is really old. Either way I wouldn’t recommend running it
A similar attack used to be able to be done in Windows by creating a batch file that calls itself at the end.
We used to do it where it would open the command prompt several times and then call itself, so after a couple seconds you would have dozens or hundreds of command prompt windows opening. On a system that only had 128 megs of RAM it didn’t take long for the system to become unresponsive.
:loop notepad.exe goto loopThen place the .bat in the startup folder
Pulling the script out of the vague recesses of my brain, what we did was more like:
ECHO pwned! start /c start.bat start /c start.bat start /c start.bat start.batThen make a shortcut, call it Internet Explorer with the blue E, and wait.
I also wrote a script that would create 1000 folders in your network drive and then change the owner so you couldn’t delete them. We used that one when people left their machine unlocked.
You’ll get a syntax error because bash functions require a space after the {
It’ll be fine after a reboot, or a killall -9 command
Hm…
fish: command substitutions not allowed hereStrange name for a catCurious if
f(){;f|f&};fworks in fish. The version in the image is bash specific, but iirc fish isn’t posix compliant so idk if posix version worksNope. Still doesn’t work.
fish: command substitutions not allowed in command position. Try var=(your-cmd) $var ... f(){;f|f&}; ^^Fish has a more explicit syntax so we would need something like
function :;:&;:&;end;:But sadly it notices and stops it
🐟🐟🐟
this was already posted 3 days ago!
oh well ~ ~ ~<3
i knew it wasn’t just deja vu…
That’s actually a bashism (defining
:as a function name). For maximum damage, usef(){;f|f&};fWhy do all my forks suddenly explode?! What have you done!
