Re:I tricked Claude into leaking your deepest, darkest secrets
by j-bos on Wednesday July 15, 2026 @05:45AM
(#48918403)
While I agree, containerization is awesome, on linux, you can just create a devUser and `sudo devUser theThing`
[ Parent
| on HN ]
Re:I tricked Claude into leaking your deepest, darkest secrets
by reactordev on Wednesday July 15, 2026 @06:55AM
(#48918942)
not the same thing. Containerization prevents devUser from accessing your machine root with its root. By containerizing, if devUser tries to sudo or su and gets a root, it will only be their root and not your root. Read up on cgroups.
Re:I tricked Claude into leaking your deepest, darkest secrets
by progval on Wednesday July 15, 2026 @07:20AM
(#48919137)
Successful sudo from a cgroup still makes you root on the machine. What you want for this is user namespaces, not (just) cgroups.
Re:I tricked Claude into leaking your deepest, darkest secrets
by reactordev on Wednesday July 15, 2026 @07:32AM
(#48919253)
yes, you would setup namespace and unshare it once mounted to isolate the sandbox so root only sees the sandbox / and not your /
Re:I tricked Claude into leaking your deepest, darkest secrets
by grosswait on Wednesday July 15, 2026 @07:21AM
(#48919143)
Why would you allow devUser sudo?
Re:I tricked Claude into leaking your deepest, darkest secrets
by reactordev on Wednesday July 15, 2026 @07:35AM
(#48919282)
normally you wouldn't but there are some instances where a script or something requires sudo in which case you would need to namespace the cgroup and do a little more work to prevent escaping the sandbox. I can think of a few cases where sudo is required for cgroups/containers from the sandbox side so it can install services and things but ideally you would isolate everything to the devUser UID or GID.