News for hackers. Stuff that matters.
Re:Detecting the use of "curl | bash" server-side by windows_tips on Sunday July 29, 2018 @12:14AM (#17636479)
>in a way that they don't stand a chance of detecting by inspection (or of having proof of after the fact)

What do you mean? They could `tee` curl output to a file (or elsewhere, for archives). They could also suspend passing the output to bash until they've verified the output (perhaps they would run a hash function and compare the result).

Re:Detecting the use of "curl | bash" server-side by Cyphase on Sunday July 29, 2018 @12:21AM (#17636497)
Then that wouldn't be 'curl | bash'.
Re:Detecting the use of "curl | bash" server-side by windows_tips on Sunday July 29, 2018 @12:30AM (#17636525)
curl | ... bash
Re:Detecting the use of "curl | bash" server-side by schoen on Sunday July 29, 2018 @12:53AM (#17636582)
The point of the article is apparently that the server can distinguish "curl | ... | bash" from "curl | bash".