Xenia rule

submitted by
she/her edited

https://piefed.cdn.blahaj.zone/posts/eM/Mc/eMMce0W84xXnkF0.png

Xenia rule
16
160

Log in to comment

Hot Top New Old

opens terminal, pauses So how fucked is my system gonna be afterwards?

 reply
38

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

 reply
26

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.

 reply
11
edited 
:loop
notepad.exe
goto loop

Then place the .bat in the startup folder

 reply
6

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.bat

Then 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.

 reply
2

You’ll get a syntax error because bash functions require a space after the {

 reply
5

It’ll be fine after a reboot, or a killall -9 command

 reply
4

Hm… fish: command substitutions not allowed here Strange name for a cat

 reply
20
edited

Curious if f(){;f|f&};f works in fish. The version in the image is bash specific, but iirc fish isn’t posix compliant so idk if posix version works

 reply
6

Nope. Still doesn’t work. 

fish: command substitutions not allowed in command position. Try var=(your-cmd) $var ...
f(){;f|f&};
 ^^
 reply
5

Fish has a more explicit syntax so we would need something like function :;:&;:&;end;: But sadly it notices and stops it

 reply
4

this was already posted 3 days ago!

oh well ~ ~ ~<3

 reply
12

i knew it wasn’t just deja vu…

 reply
1
edited

That’s actually a bashism (defining : as a function name). For maximum damage, use f(){;f|f&};f

 reply
6

Why do all my forks suddenly explode?! What have you done!

 reply
4
Insert image