logoalt Hacker News

zmmmmm • today at 5:42 AM • 2 replies • view on HN

This goes to the biggest problem imho - that we've gone this far down the track of these agents being rolled out without proper sandboxing.

The agent should not be running on the same workstation. It should have a hard isolation barrier between it and the host machine. We shouldn't be starting from a fail-unsafe state and then trying to patch in security and isolation for these people. It should be deployed fail-safe and when they hit actual friction we can solve that.

Anthropic started out doing the right thing with Cowork (running in a VM). But it seems like they've ever since been walking that back and trying to get users to rely on automatic protections. I think it's just the wrong direction.


Replies

dingdongditchme • today at 7:08 AM

The problem is that they loose some of the biggest utility that way. I want to be able to just say "draft a reply to email x". Because that is the lowest friction. I'm happy to read it back and sign-off. I don't have an answer as to how to do it securely, and am with you that the wanton disregard by big AI players for safety and security is demoralizing.

➕ show 2 replies
thinkingtoilet • today at 1:07 PM

Recently agents in two sand-boxed environments were found to be able to talk to each other using cpu caching which is fucking bonkers.

https://lumienai.com/news/openai-ai-agents-cpu-cache-covert-...

My point is your most likely not going to win here. Proper sandboxing is insanely difficult.