You must log in or # to comment.
What did the minefield directory do here to hijack cd?
Can an alias be applied upon cd?
on termux it works:
~ $ alias 'cd=echo' ~ $ cd ~ $ cd hi hi ~ $
objdump -D * | less
We have squid games at home.
Squid games at home:
The power cable would like to have a word.
it removed your disc encryption keys and the only way to recover it is finding it in memory through the minefield
while this is not real, something similar in principal very much was! (but not too widespread)
see here or look up “casino dos malware”
uh in short it erases “the disk’s” (unsure which) file allocation table (pretty much the dos/windows version of a superblock). apparently some versions did copy it to memory and give the user a chance though!
There also was Fake DOS back in the day
Has “let’s play a game” vibes
strings 1Reminder that binaries cannot change a shell’s working directory, so the non-mines will do nothing.
(
cdis a shell builtin)I mean, you can just write a whole custom shell for this
it could just reinvoke
$SHELLin the parent dirTechnically they could if run as root by modifying the parent process
Good point. Also it wouldn’t stop you from just opening another terminal window haha.
Reminds me of gameshell, which is a rogue-like game designed to teach you the unix shell. So instead of navigating with NESW, you
cdto locations. At one point you search the “garden”, which is an unmanageable tangle of directories, withfind.There goes my night? Longer?
Cool! Will give this a try for sure! Always forget commands
cat 1*a single cat is hurled unceremoniously through the window onto your lap*
I’ll hit them with an rm /etc. We go out, we go out together and on my terms.
They never guess the next move: Unplugs pc
loud knocking on the door
Either that or the PC keeps running anyway.
Boston Dynamics: “Either that or the PC keeps running away.”
I wonder if we could
bash -n -vthe source code? 🤔 Since-nshould error check without execution.Edit: maybe that only works on scripts?
Based on the responses in this thread, I feel like you could present this screenshot with a “I bet you couldn’t find your way out of this!” and a zip of the directory, and a significant number of users would voluntarily download it and extract it just to “prove that they could”.
Well yeah? And you do it in a vm. But seems like a decently simple problem anyway.
ls -aland compare the sizes.Obvioulsy whoever set this minefield thought about this
I mean they didn’t, cause you can just open another terminal window or pull the plug on the computer, but like someone else said, a binary can’t change the directory for you
cdis a shell built in, so I’m pretty sure this would be trivial to get past.The greatest trick is to make your opponent think you thought of everything. Powering off might just straight up work and they’re just bluffing, might as well try
What if it encrypts the disk when entering the dir and the only way to decrypt it is by winning? Decryption keys will be provided via API at the end.
Genuinely my first response. What are VMs for?
I run QubesOS BTW. My entire computer is just a bunch of VMs in a trench coat.
Running Qubes as a daily driver is some serious level of privacy enthusiasm
I do it mainly cos it makes managing lots of different environments easy. I can have windows and different Linux distros and different packages and cool shit all from one display manager.
Doesn’t virtualization eat away a lot of performance? Or do you not care much about it?
1-2% is the overhead of virtualization. Hardware virtualization is Goated. And QubesOS uses Zen under the hood same as what’s used by aws etc so its well optimised.
Nice
@Allero Not if it’s hardware-accelerated. You’ll be hard-pressed to find a CPU without hardware virtualization, though.
Maybe something like
find ./ -type f | xargs md5sum, then avoid the one directory where the executable has a different checksum. Heck, evenfind | lsmight suffice.This could be trivially defeated by a program which erases the hard drive unless run using a particular executable name. Then, all twenty entries could simply be hard links to the same executable file on disk, but one of the names would trigger different behavior.
So then you either cat the executable and hope it’s a shell script, you output the binary with a hex viewer and compare, you modify the executable so it’s in a lower permission group and thus wouldn’t have access to erase the drive, there’s like a hundred ways to solve this.
