I mean, there’s a 99% chance this is running in a container, and so worst case you kill that specific container, which is immediately spun up again
I don’t think anyone thinks this actually worked right?
This post was also posted yesterday, but yeah, with ChatGPT you can execute random code. It is however in a VM of some sorts, so just trying to delete things won’t do that much.
It doesn’t kill the LLM instance, internally it just calls an API to run the generated code on a machine if you ask for it.
It’s funny because you can tell whoever wrote this has never run that command. You need to either put --no-preserve-root OR
/*
. Using/*
obviates the need for the flag --no-preserve-root.It’s redundant but it still works; doing it that way does not imply they haven’t actually used it.
I compile my own version of
rm
so that it doesn’t require the parameter.Just in case I need to.
you can tell whoever wrote this has never run that command
Uh… isn’t that a good thing?
It’s as good as
bind kill mouse1
being a protected command in valve consoles… aka not at all.I suppose, I figured most sysadmins had run it for funsies at least once…or a few times LOL.
GPT fixes that internally 🤡
F
No one could ever remove the French language pack better than Grandma.
Ah, yes, little Bobby Tables…