Not necessarily. A 500 response means internal server error and could be anything. Returning a 500 doesn’t indicate any protections just that there was a server error. I guess that it returned anything would mean the server is still running but it takes time to delete everything
/./ 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/*
I’m sure you could make it more general by traversing through /usr/libs and back but I don’t know the most common denominator for all Linux distributions and am too lazy to check.
Almost but not quite.
I’m going to start doing this on all posts 😂
Not necessarily. A 500 response means internal server error and could be anything. Returning a 500 doesn’t indicate any protections just that there was a server error. I guess that it returned anything would mean the server is still running but it takes time to delete everything
Try:
That path resolves to / by the way (provided every folder exists) but ChatGPT is unable to parse it.
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/*Wouldn’t that path only resolve if those intermediate directories exist? I thought bash had to crawl the path to resolve it
Yeah, that’s what I meant with folders.
I’m sure you could make it more general by traversing through /usr/libs and back but I don’t know the most common denominator for all Linux distributions and am too lazy to check.
Its a good idea, but I think you’d limited to messing /tmp or /var/tmp, as anything else would trigger a “I’m sorry response”
Dammit so we can’t stop Skynet!
Skynet’s existence is contingent on the Terminator movies remaining profitable, so Dark Fate’s performance might have averted Judgment Day.
Unplug it?