Timeline for Is it possible to protect a bash script against a hostile environment?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 17 at 8:39 | comment | added | Kusalananda♦ | 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. | |
| Aug 16 at 18:44 | comment | added | waltinator | @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. | |
| Aug 16 at 18:26 | comment | added | Canadian Luke | Small nitpick: I have regularly ran some scripts by calling bash ./scriptname.sh without needing the execute bit set | |
| Aug 16 at 1:29 | history | answered | waltinator | CC BY-SA 4.0 |