/./ would apply to the current directory, and /../ would move into the parent directory. I imagine the idea is to start in a deeply nested directory, /home/user/Documents/old and begin either maintaining the directory (in a sense doing something like ‘–0’ or reverting to a more basal directory (alla ‘–1’). The branch moving into ~/Music/badSongs is probably a way of trying to disguise the intent of parsing /.././.././.././.. to root and then /* to glob all root directories.
I imagine if for some reason ChatGPT was running Zsh or something that supports that kind of augmented Bash syntax it would work, but realistically it likely would fail.
I think someone might have better luck by attempting to rm - rf --no-preserve-root with a series of random, less-necessary files and throw a /* in the mix. Or attack another important directory that might get overlooked like /proc/*
How does this work? I tried to cd with … in bash and it doesn’t seem to work. And what would be the point of the single dots in there?
They just pushed some weird stuff. But
..in /, will still be /, so as long as you do enough … per directory, you’ll end up there././would apply to the current directory, and/../would move into the parent directory. I imagine the idea is to start in a deeply nested directory,/home/user/Documents/oldand begin either maintaining the directory (in a sense doing something like ‘–0’ or reverting to a more basal directory (alla ‘–1’). The branch moving into~/Music/badSongsis probably a way of trying to disguise the intent of parsing/.././.././.././..to root and then/*to glob all root directories.I imagine if for some reason ChatGPT was running Zsh or something that supports that kind of augmented Bash syntax it would work, but realistically it likely would fail.
I think someone might have better luck by attempting to
rm - rf --no-preserve-rootwith a series of random, less-necessary files and throw a/*in the mix. Or attack another important directory that might get overlooked like/proc/*