News for hackers. Stuff that matters.
Re:A way to exclude sensitive files issue still open for Ope... by cowsandmilk on Sunday June 28, 2026 @09:26AM (#48707078)
If you’re already running codex as a different user to limit its file permissions, why would you add it to the docker group?
Re:A way to exclude sensitive files issue still open for Ope... by lelandfe on Sunday June 28, 2026 @09:35AM (#48707152)
A good but altogether separate note from the point I’m making: this lack of access is seen as an obstacle to overcome, and other means of access will be tried if available.

It’s a different mental model than a first party solution to “ignore” files.

Re:A way to exclude sensitive files issue still open for Ope... by TheDong on Sunday June 28, 2026 @10:34AM (#48707666)
Weirdly, the existing first party solutions around denying commands don't seem to help here.

Often enough, when one of the agents prompts for running "sudo", and I reject it, it will do what looks very much like malicious exploration to figure out how to handle things anyway, including once hijacking a separate shell's pty where I did have a valid sudo session already in order to execute some commands.

We don't yet have the capability to make these models behave in a consistent, deterministic, or safe manner yet, so a first party solution isn't even necessarily that much better. Especially if it gives a false sense of security.

Re:A way to exclude sensitive files issue still open for Ope... by lelandfe on Monday June 29, 2026 @06:35PM (#48726244)
OTOH it lets you file a bug report :)

As opposed to, "well, you should have ran it in a container if you didn't want your baby photos deleted"

Re:A way to exclude sensitive files issue still open for Ope... by jen20 on Sunday June 28, 2026 @09:53AM (#48707267)
Lack of knowledge and the desire to have it run containers for things.