2 pointsby fnoef7 hours ago3 comments
  • 6 hours ago
    undefined
  • viraptor7 hours ago
    You need to run them sandboxed in some way. Docker is one kind of solution, selinux / apparmor / sandbox-exec is another. Basically, create an environment where .env is not accessible in any way and you don't have to worry about it anymore.

    I don't care about it reading the code itself. 90% of my usage is on opensource projects anyway. The other - if I can generate something, then there's no barrier to someone else doing the same - I'm just making applications that do expected things, not doing some groundbreaking research.

    • fnoef7 hours ago
      It’s not only about the .env, but also intellectual property, algorithms, even product ideas.

      Moreover, let’s say you run a dev server with watch mode, and ask claude to implement a feature. Claude can generate a code that reads your .env (from within the server) and send to some third party url. The watch mode would catch it and reload the server and will run the code. By the time you catch it, it’s too late. I know it’s far fetched, and maybe the paranoia is coming from my lack of understanding these tools well, but in the end they are probabilistic token generators, that were trained on all code in open existence, including malware.

      • viraptor7 hours ago
        > Claude can generate a code that reads your .env (from within the server) and send to some third party url.

        Again - sandboxes. If you either block or filter the outbound traffic, it can't send anything. Neither can the scripts LLMs create.

  • coolcat2587 hours ago
    tbh im sure they do.