3 ms·
So tell us how to safely run this stuff then. I was under the impression that Docker container escapes are actually very rare. How high do you rate the chance
by simonw 1y ago
So tell us how to safely run this stuff then.
I was under the impression that Docker container escapes are actually very rare. How high do you rate the chance of a prompt injection attack against Claude running in a docker container on macOS managing to break out of that container?
(Actually hang on, you called me out for suggesting containers like Docker are safe but that's not what I said - I said "a safe container" - which is a perfectly responsible statement to make: if you know how to run them in a "safe container" you should do so. Firecracker or any container not running on your own hardware would count there.)
- simonw 1y agoI'll also point out that I've been writing about security topics for 22 years. https://simonwillison.net/tags/security/ https://simonwillison.net/tags/security/
- th0ma5 1y ago> So tell us how to safely run this stuff then. That's the secret, cap... you can't. And it's due to in band signalling, something I've mentioned on numerous occasions. People should entertain the idea that we're going to have to reeducated people about what is and isn't possible because the AI world has been playing make believe so much they can't see the fundamental problems to which there is no solution. https://en.m.wikipedia.org/wiki/In-band_signaling https://en.m.wikipedia.org/wiki/In-band_signaling
- tptacek 1y agoSeems pretty glib. Be more specific about what "can't" be done? The preceding argument was about the inadequacy of namespaced shared-kernel containers for workload isolation. But there are lots of ways to isolate workloads.