Hacker News Reader

I am sorry, but I fail to see how this would be of any help.

It is known that piping unknown scripts to bash is a bad thing. So when somebody decides to pipe into bash, they are either (1) sure of the source or (2) completely clueless about what the hell they are doing. In case (1) there is no need for the tool, and in case (2) asking "do you really want to run this?" will not make any difference since they just typed 'curl <whatever> | sh' into their shell.

View on HN

This. What if OP inspected the script and highlighted potential harmful commands? Changes in security configurations, manipulation in critical libraries, start-up scripts, and so forth. Not sure how much that would help to the novice, but it's at least actionable (user can look the commands up and understand the implications.

"What if OP inspected the script and highlighted potential harmful commands?" OP doesn't. Look at the code.

That's exactly what he says, he agrees with you and just offers a suggestion on how to improve the script.

Reply on news.ycombinator.com