Conversation

Jarkko Sakkinen

Landstrip 0.3.0 now fully implements Anthropic's file system policy with Landlock rules, and most of the network policy with Landock network rules and a simple seccomp broker that processes bind() and connect() system calls.

The only feature that is missing is allow and deny lists for domains.

I wanted to see where Landlock scales also in order to consider whether root namespace kernel patch set makes sense or not.

https://crates.io/crates/landstrip/

I already was a bit skeptic about rootns in Februrary but agent-as-an-adversary scenarios require more airtight security. It's not the smartness, which is worrying, it's the reaction time to the environment. Races cannot exist.
1
0
0

Jarkko Sakkinen

Edited 15 days ago
How I would recommend to host coding agents is:

1. Have something granular in detail but simple (e.g. like Landstrip or Anthropic's own sandbox runtime). This is for protecting files in your home directory for the most part.
2. Wrap that with a container with a disposable rootfs and passwordless sudo. This protects the system from damage that you statiscally will get when being ignorant. The statistics are not on your side in this over long period of time.

For the latter, using Google's gVisor is overall great and secure option. I made a example/reference of this container setup: https://github.com/puavo-org/container-agent
0
0
1