

2·
22 hours agoIt’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.
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.
Most people expect a domain to work without adding 8080 as a port number in the URL. Hell, I’d say a majority don’t even know that it’s possible.
That’s not going to happen with the current tech. Maybe someone comparable comes out with those specs.
For the same reason you compare things lightly to the holocaust. At some point the word looses the gravity of it’s meaning.
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.