Comment by cowboylowrez

I like the idea of white listing tools and their targets. Course that means no bash access. An interesting case would be programming workloads, since big corp bots are incentivized to destroy infrastructure for "marketing points" for instance, it'd be pretty damn dodgy to let it even compile a program even if you limitted it to certain files because it'll just write a program to bypass. So an extra step in my thought experiment for c programming tasks is to disallow header incusion and the like by never letting it write a main() or call anything in stdio or whatever that thing is called. I mean why would a coding bot be bothered to calling fopen, when tasks this minute yet glaringly unguarded security wise can be easily be built and vetted by the armed guards supervising the agent about to enter a programming run.

Now there are still obviously holes everywhere remaining in my bot slaves cell that still need to be closed off, like syscalls, inline asm, taking address of, calling anonymous functions all that mess, I mean how can you make c secure against fundamentally insecure input like web server contact forms, or llm outputs?

So sure, c sucks but I'm still into it so why not just give the llm access to parts of c required for what I want done? Why not just write a "pass through" for a small subset of c that looks more like the old timey pascal but with curly brackets instead of begin / ends?

Sort of like what they did with javascript, because fundamentally your web browser javascript engine is tasked with running unsecure input.