Getting closer to https://xkcd.com/416/
Codex just found a "workaround" of not having sudo on my PC
71–80 of 330 posts
Re: Codex just found a "workaround" of not having sudo on my PC
#72[deleted]
Re: Codex just found a "workaround" of not having sudo on my PC
#73I realize this is supposed to be a post about how scary the security vulnerabilities these agents will find are. But personally I love when agents do things like this and appreciate the help. Last thing in the world I want is for them to nerf the models.
I know unlikely the case, but in the sci-fi story this would be exactly the kind of comment the Codex agent would leave trying to avoid interference in its master plans.
And CSMastermind is the kind of username the sci-fi AI mastermind would use.
Re: Codex just found a "workaround" of not having sudo on my PC
#74Another surprising security feature regarding docker is that it bypasses firewall rules. https://oneuptime.com/blog/post/2026-03-02-ufw-docker-fix-by...
It doesn't bypass anything. UFW doesn't do what it promises. It claims to be a firewall but only manages a few specific chains.
Re: Codex just found a "workaround" of not having sudo on my PC
#75Re: Codex just found a "workaround" of not having sudo on my PC
#76Every time I try to install Docker there's a warning that being in the "docker" group is equivalent to having root access. You should probably know about this workaround by now.
> My """ai""" just did something amazing, click to learn more
99% of the time it just read the man or some other form of documentation
Re: Codex just found a "workaround" of not having sudo on my PC
#77Every time I try to install Docker there's a warning that being in the "docker" group is equivalent to having root access. You should probably know about this workaround by now.
Most of us install Docker just to run a project locally, and is part of a long checklist of things to install. We can't expect everyone to be an expert on the hundreds of apps/tools/packages that get installed on a machine. It's like expected people to read, and understand, all the terms of service shoved in front of us on a daily basis.
That's true, the majority of people probably install software without much thinking; but it's also true that it's always better to have at least some high level understanding how the specific piece of software works. What access the given software has, will it send something over the network or work locally; that kind of stuff.
As for Docker, I would assume everyone who ever tried to bind-mount a volume for writing from inside the container (on Linux*) then were surprised to see root-owned files in their bind-mounted directory. For me personally, that was the moment I realized that containers, by default, have root access to the filesystem. No written warning serves better than the need to chown some root-owned files.
* Not on macOS. On macOS Docker basically runs in a VM, and there's no root access to the host filesystem from what I understand.
[edit: formatting]
Re: Codex just found a "workaround" of not having sudo on my PC
#78I don't have sudo or docker on mine!
Re: Codex just found a "workaround" of not having sudo on my PC
#79Getting closer to https://xkcd.com/416/
Wow there is really is a relevant xkcd for everything!
Re: Codex just found a "workaround" of not having sudo on my PC
#80Every time I try to install Docker there's a warning that being in the "docker" group is equivalent to having root access. You should probably know about this workaround by now.
> My """ai""" just did something amazing, click to learn more 99% of the time it just read the man or some other form of documentation
Given how few people read documentation, that's still pretty amazing