• 0 Posts
  • 77 Comments
Joined 2 years ago
cake
Cake day: June 13th, 2024

help-circle
  • I think the gun analogy does not really work here: you cannot be held accountable for creating any part of a gun, in case of a murder.

    You’re not making the gun, the programmers that wrote the DDoS program did. You’re firing it.

    It’s more like, you and a bunch of your friends murder by getting together and flinging the victim with rubber bands until the victim actually dies. Just because all you did was fling a small percentage of the rubber bands and that wouldn’t have killed the victim on your own doesn’t change the fact that you participated in and committed a murder. Legal systems do not have loopholes that allow you to commit crimes like this. They only have loopholes for the ultra wealthy.





  • Yeah, great, except the bot can literally just write whatever it wants to the config file ~/.openclaw/exec-approvals.json and give itself approval to execute bash commands.

    There’s probably a hundred trivial ways to get around these permissions and approval requirements. I’ve played around with this bot and also opencode, and have witnessed opencode bypass permissions in real time by just coming up with a different way to do the thing it is wanting to do.





  • Yeah I’m not saying its perfect and LLMs are non-deterministic so it could give you some crap. You’re not wrong and it’s good to be aware of that. How do you verify some random stranger from the internet wasn’t an asshole and gave you malicious config? 🤷 The best answer is probably just that OP should heed the warning on the website they linked, if they have no confidence or relevant skills:

    THIS IS DELIBERATELY MALICIOUS SOFTWARE INTENDED TO CAUSE HARMFUL ACTIVITY. DO NOT DEPLOY IF YOU AREN’T FULLY COMFORTABLE WITH WHAT YOU ARE DOING.

    I pasted the OP unmodified into a local LLM and it gave me this:

    Paste this (replace  192.168.1.105 with your Acer’s local IP from Part 1.3): 
    
    server {
        listen 80;
        server_name wowsocool.com www.wowsocool.com;
    
        location / {
            proxy_pass http://192.168.1.105:8000/;
            proxy_set_header Host $host;
            proxy_set_header X-Real-IP $remote_addr;
            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header X-Forwarded-Proto $scheme;
        }
    

    along with correct instructions on finding the IP of the laptop, port forwarding, and examples on how to set up DDNS for several popular providers. The only thing I can see that is wrong is the port should be 8893 instead of 8000 and they may want to proxy a different path to Nepenthes than /


  • theunknownmuncher@lemmy.worldtoSelfhosted@lemmy.worldA dummy's request for Nepenthes
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    1
    ·
    edit-2
    2 months ago

    Nah, they suck for programming or anything involving imperative logic, but they are pretty decent with things that are declarative, like config. I know people want to hate or deny any usefulness of LLM, and it doesn’t help that corpos insist on cramming LLMs into usecases that aren’t applicable to LLMs at all, but this is actually one of the things they are good at.