@GuillaumeRossolini@infosec.exchange
@jerry@infosec.exchange @lerg@infosec.exchange also, assuming this is bash or equivalent, these shells tend not to default to set -e if memory serves? Meaning βexit as soon as you get a failed commandβ: this isnβt the default.
Another flag I discovered recently is set -o pipefail which has the same effect for piped commands, because that isnβt covered by -e for some reason.
So a failed directory creation would let the remainder of the script run, like you said, without extra checks (or these flags)
@GuillaumeRossolini@infosec.exchange
@jerry@infosec.exchange @lerg@infosec.exchange still another failing of these tools, they arenβt really absorbing the boring tasks (the quality checks) that were hidden in the prompt