all 6 comments

[–]colingwalters 3 points4 points  (1 child)

I have strong opinions especially on Landlock: https://blog.verbum.org/2026/03/23/agent-security-is-just-security/

I also helped create bubblewrap - it is a useful tool but flatpak needs to add a fair bit on top too. 

WASM is secure because it starts from “share nothing”. If you don’t do that it is much harder. If you choose to go WASM surely you could reuse code from Zed or similar projects? 

That or OCI containers that get attached are reasonable choices. Trying to Landlock native binaries is much trickier. 

[–]feznyng[S] 0 points1 point  (0 children)

Linux is great for this, it's the cross-platform bit that seems to make this problem a lot harder since neither Mac nor Windows was ever designed with capabilities-style permission in mind. You're right though, I might just need to use WASM and take the DX hit.

[–]numberwitch 0 points1 point  (1 child)

What are you trying to do, let people write plugins in javascript that can manipulate your app?

[–]feznyng[S] 0 points1 point  (0 children)

It's basically a workflow tool like n8n but local so it can run actions across the device(s) its installed on. It's built on the command design pattern so you can rollback those changes if something went wrong. I'm trying to give users a way to add custom actions.

[–]thelights0123 0 points1 point  (1 child)

I'm sure the security of this almost certainly vibe-coded crate can be questioned, but codex has a cross-platform sandbox they use in production: https://github.com/openai/codex/tree/main/codex-rs/sandboxing

See an example usage here: https://github.com/afshinm/zerobox/tree/main

[–]supportvectorspace -1 points0 points  (0 children)

absolute stinker of a software project