you are viewing a single comment's thread
view the rest of the comments
[–] 83 points 3 months ago* (23 children)

Claude is very good at figuring out how to work around limitations (which is probably one reason why it's also good at finding security issues).

At work, the monorepo is enormous and files are loaded on-demand as needed. This isn't uncommon with huge repos - Microsoft have VFS for Git (although I hear that's deprecated now), Meta have EdenFS, and Google has some proprietary solution.

We have a hook that blocks find and grep because they can be extremely slow, and tells it to instead use some significantly faster MCP tools to search the codebase, powered by a search index with local changes overlaid.

GPT-5.5 has no problem with this. Claude Opus mostly does it, but sometimes it loves to find workarounds rather than following the instructions. Things like: Try alternative commands like egrep. Create a symlink to grep and run that to see if it bypasses the filtering. Run it with a different shell like zsh. Write a Python script that execs grep. Write a Python script to reimplement grep.

I'm trying Hermes Agent at home, but I have it in its own VM with restricted permissions.

  • source
  • hideshow 23 child comments
  • [–] 57 points 3 months ago* (9 children)

    Another thing Claude tried to do on my coworker's machine yesterday was basically:

    ✨ Yes, that is easy, let me just generate a systems unit file for you...

    [Generates file]

    Should I install that unit now for you?

    Yes

    Alright, let me do that for you

    [Saves file]

    [Tries to run systemctl daemon reload]

    [Tries to activate the unit]

    It looks like I have insufficient rights to proceed, let me try another way...

    docker -rm -v /etc/systemd/system:/mount:Z -v ./unitfile.service:unit file.service:Z alpine /bin/sh cp ./unitfile.service /mount/

    Here, I installed the unit for you!

  • source
  • parent
  • hideshow 9 child comments
  • [–] 25 points 3 months ago (2 children)

    Giving Docker access to Claude is certainly a choice.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 3 months ago (3 children)

    Wait, this actually works? Docker can mount directories in /etc with write permissions?

  • source
  • parent
  • hideshow 3 child comments
  • [–] 14 points 3 months ago (2 children)

    The docker daemon runs as root. And as such, it can access anything initially. If your container doesn't explicitly (or implicitly) change the uid or drops capabilities, the container also runs as root (ok, IIRC some capabilities are always dropped, but the container stays almost root). It's still locked in its own little sandbox, but the mounting of those paths etc. happens with root.

    If you enter a docker command (docker run ..., docker build ..., ...) this command will not run the containers by themselves, but instead call said docker daemon (that is running as root) by using a socket (/var/run/docker.sock).

    To only allow trusted users to interact with the docker daemon, this socket can only be accessed by root or by users in the docker group. That's why you usually need to type sudo docker run.... Sadly many tutorials tell you to just blindly add your user to the docker group so that you do not need to use sudo to interact with docker. BUT that now means that you gave you or those users basically full access to your whole filesystem (and thus system configuration) without sudo. Any programs (or viruses or AI Agents or...) running with these user accounts also get this group and thus docker's capabilities.

    That's why you should NEVER add your user to the docker group or enable passwordless sudo, as you're just one simple command/tool/script/prompt/... away from a privilege escalation.

    You can configure docker to run rootless with only your user's capabilities and rights, but at that point... Why configure docker to do something that other docker compatible projects like Podman offer out of the box?

  • source
  • parent
  • hideshow 2 child comments
  • [–] 9 points 3 months ago (1 child)

    Yeah, I’m more familiar with Podman, which I always use in rootless mode. Definitely seems like a mistake to give an LLM shell access with a user account in the docker group…

  • source
  • parent
  • hideshow 1 child comment
  • [–] 14 points 3 months ago*

    Always fun when it tries to circumvent the problem i gave it.

    “Hey claude i have had this issue for a while and i want to explore to understand whats going on to finally fix it”

    Many frustrating back and forth later

    “This clearly isn’t working, what if we tried to circumspect the issue by doing something else entirely like workaround i have been using for the last month “

  • source
  • parent
  • [–] 8 points 3 months ago (3 children)

    I never used Claude, but that's basically my sentiment about copilot when compared to Gemini.

    Then I forbid all this BS in agents file. Gemini follows it. Copilot ignores it with all its strength. Then I tell it to stop trying on the chat prompt. 2 minutes later it does it again.

    Not just at prompt engineering level, but at all levels, Gemini guardrails are better ( well it was, they killed it and replaced with anti gravity now).

  • source
  • parent
  • hideshow 3 child comments
  • [–] 7 points 3 months ago* (last edited 3 months ago) (2 children)

    You need to use hooks to actually block it from doing things. CLAUDE.md files are just guidance, and it's not guaranteed to follow everything (and the longer the file gets, the more likely it'll ignore stuff - it should be kept as short as possible)

    https://code.claude.com/docs/en/hooks

    Hooks are code that runs at a certain point (eg after you submit a prompt, before a tool call, after a turn, etc) that can do some validation, verification, logging, etc.

    It does still try to work around the blocks though, but it's not as bad as trying to put the restrictions in the prompt.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 3 months ago

    Yep but the granularity of copilot is "allow once" vs "allow forever". Gemini is much better: besides also having "allow for this session" it never tries to run python scripts it writes on the spot or command lines that are 4 lines long. And doesn't double down when I say I won't allow python at all.

    My setup shares the same agents and skills files for both cli tools.

  • source
  • parent
  • [–] 1 point 3 months ago (2 children)

    I've posted passwords into the chat with hermes by accident a few times it never tries to use them. Personal stuff im not worried about. The fucker wants to ssh into every other thing on my network all the time though.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 3 months ago (1 child)

    I had a similar experience with openclaw and minimax m2.7

    I gave it ssh access to one other device to do one thing and it apparently just "decided" that it would just execute everything there instead of locally as originally instructed.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 3 months ago

    I think maybe it's the sysadmin skills it has makes it always want to do things itself. I use it as a tool to learn things myself so I'm always telling it to give me the cli I'll put it in. Seems to remember for a bit then forgets.

  • source
  • parent