I used to think the same, but apparently there's a way to differentiate between curling into bash and curling into a text file.
replySo you could be diligent and curl into a text file, see nothing is wrong, but then when you curl into bash, it runs something different.
Being diligent means that you curl into a text file, see nothing is wrong, and then run the file instead of curling again.
replyI think the difference people were warned about is that the server can infer the client, so there would be a difference between reading it in your regular browser and curling. As the other commenter says, I'm not sure how the server would be able to tell what curl does with the response.
reply curl > some_file
bash some_file
Edit: thanks for the replies, that makes perfect sense
reply
Timing. A megabyte of "sleep 10;" would be read from the server more slowly when piped to bash versus written to a file
replyNo but we use MCP so we’re fine.
reply