News for hackers. Stuff that matters.
Re:Detecting the use of “curl – bash” server side (2016) by londons_explore on Wednesday December 09, 2020 @06:01AM (#25357371)
The difference between a malicious and a legit bash script can be just a couple of characters. Eg. the script can have a deliberate injection vulnerability in a variable expansion...

If people commonly inspected bash scripts they downloaded, attackers would just write the script more carefully to make sure 15 minutes reading the script wouldn't find anything bad going on.

Re:Detecting the use of “curl – bash” server side (2016) by prepend on Wednesday December 09, 2020 @06:47AM (#25357631)
Fortunately it’s not common, so they don’t. If it became common and they did, I could inspect the script using automated tools that check for obfuscation, etc.

I think it’s not about eliminating, but making a little better. With lots of this stuff, it’s just about being faster than the other guys that the bear is chasing.

It’s kind of moot because all this is solved by “don’t download and run scripts from strangers.” Then you just have to worry about someone rooting homebrew.

I don’t like this line of thought because it ultimately gets us to a Microsoft world where everything is signed and there’s still tons of crap getting through.

I’d rather have it where scripts can be individually assessed and run without lots of expensive stuff in the middle. Even if that means some risk.