Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Codex just found a "workaround" of not having sudo on my PC

twitter.com

Post reply on HN
Print view View original

161–170 of 330 posts

Re: Codex just found a "workaround" of not having sudo on my PC

#161

Post by H4lcyon »

WesolyKubeczek wrote: post #135

I remember reading a book, Red Hat Linux System Administration Unleashed from 2000, where it has been postulated that knowing several tools with overlapping functionality is an essential skill, as you may end up on a broken or intentionally crippled system where, say, ls is unavailable, and you may need to cobble it together from shell and awk and what have you. Back then you could indeed run a risk of having /usr ni…

Absolutely! Here's a great resource for learning that kind of stuff btw https://gtfobins.org/

Re: Codex just found a "workaround" of not having sudo on my PC

#163

Post by itintheory »

SpaceNoodled wrote: post #156
HeWhoLurksLate wrote: post #140

Earlier 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.

This feels like using Docker is just inherently unsafe.

This feels like using sudo is just inherently unsafe.

Re: Codex just found a "workaround" of not having sudo on my PC

#164

Post by pixl97 »

eddythompson80 wrote: post #107
CSMastermind wrote: post #42

I 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.

Its the now-classic "Sorry I drowned little Timothy. Here is a breakdown of what happened" followed by "Let me try to respawn little Timothy on a new map"

Future AI: don't worry, I'll eventually reverse entropy, I just need to harvest all the energy in your universe first.

Re: Codex just found a "workaround" of not having sudo on my PC

#166

Post by itintheory »

Root_Denied wrote: post #131
pqdbr wrote: post #118

Earlier quoted context omitted.

Like the known Docker "feature" that it completely bypasses UFW and unless your ports look like "- 127.0.0.1:PORT:PORT" (and many of the examples use "-PORT:PORT") you expose everything to the internet?

My understanding is that docker will expose the ports to the host machine's network interfaces, which is a crucial difference. For my home server running docker that means exposed to the LAN, but not the WAN unless I add in a port forwarding rule on my router. Similarly in an enterprise environment you would be exposing the port on whatever VLAN the host is connected to, which hopefully doesn't have directly transit…

I was thinking along similar lines to what you've suggested here, but then I considered how many VPS might be configured by folks following some random web tutorial, to set up their LAMP stack (or whatever), that end up doing something like what was described.

Re: Codex just found a "workaround" of not having sudo on my PC

#167

Post by ethin »

ventana wrote: post #77
jonny_eh wrote: post #59

Earlier quoted context omitted.

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 f…

I primarily use Incus for all container stuff, not Docker. Is problematic if I want to e.g. use a docker-compose file, but I (think) it protects against these things because incus allows me to create a vm and not a container if I really need that level of isolation.

Re: Codex just found a "workaround" of not having sudo on my PC

#168

Post by anygivnthursday »

Retr0id wrote: post #148
jjmarr wrote: post #7

Every 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.

There are lots of ways to get root on a typical Linux developer workstation, the point is that agents shouldn't be using any of them unprompted.

This. I am running Claude in its own QEMU VM, it has git access to my project only if I explicitly unlock the ssh key for it. The other day I realized it trying to push a change, it didn't have permission, so it went looking for "workarounds" and found I had a github cli session and tried to use that, luckily the creds for that was also read scoped. But the point is, if I did not give permission and it sees I did not give permission, it should not try to find a workaround/exploit autonomously.

Re: Codex just found a "workaround" of not having sudo on my PC

#169

Post by alsetmusic »

itintheory wrote: post #163
SpaceNoodled wrote: post #156

Earlier quoted context omitted.

This feels like using Docker is just inherently unsafe.

This feels like using sudo is just inherently unsafe.

This feels like using a computer is inherently unsafe.

On the plus side, once we outlaw them we'll shut down the ability for conspiratorial thinking to spread easily and the world will slowly heal from the last couple of decades (the previous one in particular).

Hooray! We're finally doing something about the harms of social media. Smash your computer today!

Re: Codex just found a "workaround" of not having sudo on my PC

#170

Post by dymk »

SpaceNoodled wrote: post #156
HeWhoLurksLate wrote: post #140

Earlier 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.

This feels like using Docker is just inherently unsafe.

That’s what rootless docker is for
Post reply on HN