It’s even worse. The server can detect if you are piping it straight into a shell or just downloading the file. It can then send different scripts based on that.
Curl has a limited buffer and bash reads a line and then executes it, before reading the next line.
So first you need a command that takes time if executed. So a delay, downloading a big file, user input work. Next you fill up the buffer. Just your normal script. Maybe some comments etc.
Now the server can detect if after the first kB the stream stops.
It’s even worse. The server can detect if you are piping it straight into a shell or just downloading the file. It can then send different scripts based on that.
How can it see that? If possible, isn’t that a flaw of curl? I don’t see a good reason for the sever to know what you’re doing with the file
Curl has a limited buffer and bash reads a line and then executes it, before reading the next line.
So first you need a command that takes time if executed. So a delay, downloading a big file, user input work. Next you fill up the buffer. Just your normal script. Maybe some comments etc.
Now the server can detect if after the first kB the stream stops.