Earlier quoted context omitted.
Yes, it is worse because using your package manager trusts your distribution (and the packages packager), doing curl bash trusts a random website. While in this case docker is not a random website, it's best to use the package manager when available
> Yes, it is worse because using your package manager trusts your distribution (and the packages packager), doing curl bash trusts a random website. Is installing docker from docker own APT repo actually safer than curling a binary from docker's website?
Codex just found a "workaround" of not having sudo on my PC
301–310 of 330 posts
Re: Codex just found a "workaround" of not having sudo on my PC
#302Earlier quoted context omitted.
I'm more worried about my `~/.aws` and `~/.ssh` folders. People who use IDE-based AI tooling with IDEs that support dev-containers have no excuse for not leveraging dev containers, both for preventing agents losing your data and defending against secrets-harvesting supply-chain attacks
Using containers as a security boundary is inexcusable.
Re: Codex just found a "workaround" of not having sudo on my PC
#303Earlier quoted context omitted.
Please stop spreading this toxic curl|sh nonsense. It's wildly corrosive to security and system stability.
Is it really that much worse than using a package manager that drops a binary that you're not going to inspect anyways?
Re: Codex just found a "workaround" of not having sudo on my PC
#304Earlier quoted context omitted.
wait so just being lazy and using sudo on Docker commands instead of figuring things out actually means I'm being safer? awesome.
No, because a malicious AI agent could just replace the sudo binary in your path with one that collects your password and uses it to execute arbitrary code as root. Nothing short of sandboxing everything or just never using AI agents or proprietary software will prevent this.
Re: Codex just found a "workaround" of not having sudo on my PC
#305Earlier quoted context omitted.
I'm more worried about my `~/.aws` and `~/.ssh` folders. People who use IDE-based AI tooling with IDEs that support dev-containers have no excuse for not leveraging dev containers, both for preventing agents losing your data and defending against secrets-harvesting supply-chain attacks
Using containers as a security boundary is inexcusable.
Re: Codex just found a "workaround" of not having sudo on my PC
#306Earlier quoted context omitted.
That works great if it's one agent, absolutely doesn't if you want to tackle something complex that warrants using ..say.. ten agents. I can imagine a future where this technology empowers you to do things with a thousand agents.
You can have ten thousand agents, you will always have 1 agent in charge of, say, reading the file in a distant directory, and this agent (which will have minimal context) should be smart enough to realise that this action is unusual. I'm not sure what is your point: are you saying that in a multi-agent workflow, you will have one agent per letter read on the file? I would assume that each agent as a specific unitary…
The idea is not that you parallelize simple tasks. With a thousand agents, eventually, once we figure out how to orchestrate agents for real, you can tackle significantly more complex projects.
Here's a random example - writing an OS kernel from scratch, porting a good subset of Linux drivers automagically, developing a passable userspace, testing on ten VMs with different hardware configuration.
We can't do this yet, of course. But when we can, these thousand agents can't ask you every time something goes wrong. That just doesn't scale.
This 'getting stuck once every ten-fifteen minues' is very much the experience trying to develop complex software with codex or Claude code right now.
Re: Codex just found a "workaround" of not having sudo on my PC
#307Earlier quoted context omitted.
That's why adding your user account to the docker group is a separate step that explicitly does not happen as part of the installation: https://docs.docker.com/engine/install/linux-postinstall/ > Warning > The docker group grants root-level privileges to the user. For details on how this impacts security in your system, see Docker Daemon Attack Surface.
wait so just being lazy and using sudo on Docker commands instead of figuring things out actually means I'm being safer? awesome.
Re: Codex just found a "workaround" of not having sudo on my PC
#308Earlier quoted context omitted.
You can. Would it surprise you to know that this, too, is often locked down?
That sounds terrible! Feels like your LLM agent probably has more control over your computer than you. Can't imagine being confined to a prison like that, but I suppose there are other aspects (monetary or otherwise) of the job that make up?
Re: Codex just found a "workaround" of not having sudo on my PC
#309Re: Codex just found a "workaround" of not having sudo on my PC
#310Earlier quoted context omitted.
> 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