>in a way that they don't stand a chance of detecting by inspection (or of havin... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		windows_tips on July 29, 2018 \| parent \| context \| favorite \| on: Detecting the use of "curl \| bash" server-side >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).

Cyphase on July 29, 2018 [–]

Then that wouldn't be 'curl | bash'.

windows_tips on July 29, 2018 | [–]

curl | ... bash

schoen on July 29, 2018 | | [–]

The point of the article is apparently that the server can distinguish "curl | ... | bash" from "curl | bash".

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact