this post was submitted on 18 Oct 2025
432 points (97.8% liked)

Linux

11649 readers
562 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Flipper@feddit.org 2 points 3 months ago (1 children)

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.

[–] Railcar8095@lemmy.world 3 points 3 months ago (1 children)

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

[–] Flipper@feddit.org 3 points 3 months ago

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.