3 ms·
Sandboxing issue can be solved by extending cmake with a directive specifying which paths are accessible up front. I might be willing to do a PR soon
by loa-in-backup 8y ago
Sandboxing issue can be solved by extending cmake with a directive specifying which paths are accessible up front.
I might be willing to do a PR soon
- dahart 8y agoYes. This isn’t quite what the author was talking about though. They used the term “sandboxing” to mean that dependency rules in the build system can act on things that they don’t depend on. You’re talking about a higher level sandboxed view of the file system. The kind of sandboxing you’re talking about can be mostly solved for any build system with some wrapper shell scripts, or an environment shell script. That’s how most people are doing it. At my work, there’s a crazy sandboxing system for Linux written as a C program that actually creates an environment with a modified file system, and access to certain paths is strictly enforced... no process launched from inside this environment can access anything but the whitelisted paths, by any means. This is a very heavy hammer, and I suspect over the top and unnecessary. OTOH, this definitely prevents mistakes, and my company is large. I don’t know the history here, but the existence of a system like this leads me to assume there must have been some large and real pains that lead to the development of a heavy-handed sandbox.