• Elvith Ma'for@feddit.org
    link
    fedilink
    English
    arrow-up
    6
    ·
    3 hours ago
    ~$ sudo eat -rm ./Homework
    
    @crank0271@lemmy.world is not in the sudoers file. This incident will be reported.
    

    sigh

    ~$ groups
    crank0271 docker
    
    ~$ docker run -rm -v ./Homework:/mnt/Homework --entrypoint '/bin/sh' alpine:latest -c 'sudo eat -rf /mnt/Homework'
    
    • Dave.@aussie.zone
      link
      fedilink
      English
      arrow-up
      2
      ·
      2 hours ago

      ~$ groups crank0271 docker

      ~$ docker run -rm…

      No joke, this is exactly what LLMs will do if they can’t do something directly.

      • Elvith Ma'for@feddit.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        39 minutes ago

        This is why I told some colleagues several times to NOT put their user into the docker group AND to set the docker command for Claude at least to ‘ask every time’.

        That fucker circumvents your guardrails all the time. “Oh I’m not allowed to read a .env file with the harness? Let’s check cat .env!” Yesterday Claude even wrote a little python script to try to print the .env file, because he thought he’d need it to debug a container. (Spoiler - the problem wasn’t even with some env vars and also the .env was just filled with dummy values as it is an example from a public repository anyways).