It is unlikely to be a real concern, since an attacker having the possibility to edit a pipeline can easily execute any command, but at least our step won't be involved
10 lines
140 B
Bash
Executable File
10 lines
140 B
Bash
Executable File
#!/bin/bash
|
|
|
|
set -eou pipefail
|
|
|
|
error() { echo -e "\\e[31m✗ $*\\e[0m"; }
|
|
|
|
if [ ! -f "$1" ]; then
|
|
error "File '$1' not found"
|
|
exit 1
|
|
fi |