Optional hardening: seccomp to prevent network access for all tooling #21
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Tooling exists specifically to be used offline, and there's a decently large attack surface area exposed via the libraries it uses and formats that are processed (particularly
assimp, alsobasisumaybe).As a bit of security paranoia, it might be worth aggressively sandboxing these tools.
I'm using the tools in a worker process and providing isolation through said workers environment (and any reasonable engineer should do the same for any production service that deals in untrusted data!) but double-dipping here is essentially free.