HN Reader
New
Top
Best
Ask
Show
Job
Allowlisting some Bash commands is often the same as allowlisting all
37
25
9 days ago
by drewgregory
Allowing a "command" (executable, I believe) that isn't a read-only absolute path is a fool's errand. I will modify PATH and run my own implementation of it.
9 days ago
by sadnboxx
Same thing for allowing specific sudo-commands. Many tools (like vim or the tools mentioned in the article) would have the same problem when allowing them to be run with root privileges.
9 days ago
by zufallsheld
True, you can do almost anything if
find
is allowlisted.
find / -exec sh -c 'whatever u wanna do' \;
5 days ago
by with
I remember when I was starting out, someone on my team showed me, that in the case where we were allowed to run vi and root on a machine there was noting stopping one from just starting a child shell from within vi with root privileges.
4 days ago
by totetsu
I know they’re just being through but the “go test” part is a bit “Pray, Mr Babbage”… Test code is just code. I know of no language where tests are sandboxed in any meaningful way.
9 days ago
by pimlottc
> I really thought `eval` would not be abused on non validated input
- your colleague, or you 1 year before.
9 days ago
by hbogert
“…with Claude Code”
9 days ago
by teddyh
Not entirely related to the content but
man
'allowlisting' reads so badly. We should just out of ease of reading return to whitelisting.
4 days ago
by AllegedAlec
everything
is a container these days, and yet somehow collective-we don't manage to have AI agents run in a container layer on top of our current work, so we can later commit or rollback?
9 days ago
by eqvinox
I'm sorry but the idea of giving an AI agent a non-restricted shell is
insane
. If you don't want it to perform certain commands those commands should not be in its environment at all.
4 days ago
by bandrami