Re:OpenWorkers: Self-Hosted Cloudflare Workers in Rust
by andrewaylett on Thursday January 01, 2026 @02:11PM
(#46457026)
Cloudflare needs to worry about their sandbox, because they are running your code and you might be malicious. You have less reason to worry: if you want to do something malicious to the box your worker code is running on, you already have access (because you're self-hosting) and don't need a sandbox escape.
[ Parent
| on HN ]
Re:OpenWorkers: Self-Hosted Cloudflare Workers in Rust
by AgentME on Thursday January 01, 2026 @06:27PM
(#46459382)
Automatically running LLM-written code (where the LLM might be naively picking a malicious library to use, is poisoned by malicious context from the internet, or wrongly thinks it should reconfigure the host system it's executing code on) is an increasingly popular use-case where sandboxing is important.
Re:OpenWorkers: Self-Hosted Cloudflare Workers in Rust
by andrewaylett on Friday January 02, 2026 @12:20PM
(#46467028)
That scenario is harder to distinguish from the adversarial case that public hosts like Cloudflare serve. I don't think it's unreasonable to say that a project like OpenWorkers can be useful without meeting the needs of that particular use-case.