Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • 1
    Small nitpick: I have regularly ran some scripts by calling bash ./scriptname.sh without needing the execute bit set Commented Aug 16 at 18:26
  • 1
    @CanadianLuke ./scriptname.sh still must be readable. There's bash -x ./scriptname.sh, but, if you're blindly executing scripts from elsewhere, without reading/understanding them, you're at risk. Commented Aug 16 at 18:44
  • 4
    In a "hostile environment", I wouldn't even trust the system's bash interpreter to be friendly. All data that a script processed in such a place would be compromised. Likewise for a statically compiled binary. Commented Aug 17 at 8:39