It's kind of hilarious seeing content like this make the rounds. I am sure that this will be a hot topic this month.
I personally don't think a technically-minded person should have any difficulty setting up a secure openclaw/moltbot/clawdbot instance. If you aren't savvy with operational security concepts, you definitely should not be trying to host your own openclaw and connecting it to the wild.
A few tips from me:
- Set it up on an isolated server on a separate user account. There is no risk there of it running wild on personal files or data. All of this talk about running it on your home machine & account makes me throw up a little bile every time I read it. Absolutely imbecilic idea.
- Do not run it under your own user instance (which typically tends to be in the sudoers list)--please don't be fucking stupid folks. Use a dedicated account without access to your personal user account's data.
- There is no real need for you to expose any kind of access to it externally via your firewall. Use tailscale if needed and lock down your tailnet and the openclaw service (use serve, not funnel).
- Do you *really* need to give it full access to all these skills? For example, giving it write access to your Google Workspaces? Use your brain and don't blindly follow these half-baked "tutorials" you see permeating the internet right now--most of these are written by absolute morons who have no fucking clue what they're doing or the implications of it.
TL;DR: just use common sense. It can be a neat tool but there is no need to expose yourself
View quoted note →