Are prompt injections solved? If OpenClaw is only useful when it has access to your digital life, then why does it matter where it runs? You might as well be asking me to keep my dead man's switch safely on the moon. If you find this software useful, you are sharing a count down to a no good very bad day with everyone else who finds it useful. One zero day prompt injection technique, your e-mail on a distribution list, and that's all she wrote.
Setting up OpenClaw on a cloud VM
21–30 of 69 posts
Re: Setting up OpenClaw on a cloud VM
#22It's really not that hard to run them in docker. Can give them a nestybox (with a little work) sidecar so they can run docker-in-docker. As far as permissions, the only mental model that makes sense to me is treating them like actual people. Bound their permissions in the other systems not on their own machines, basically zero trust. For instance for email, most mail apps have had delegated permissions for a while, e…
You still have to trust your executive assistant. I would never give someone I don't trust the ability to read and write emails for me.
Re: Setting up OpenClaw on a cloud VM
#23Are prompt injections solved? If OpenClaw is only useful when it has access to your digital life, then why does it matter where it runs? You might as well be asking me to keep my dead man's switch safely on the moon. If you find this software useful, you are sharing a count down to a no good very bad day with everyone else who finds it useful. One zero day prompt injection technique, your e-mail on a distribution lis…
It's a bit like the xkcd where the admin account is secure but all the useful information is in the user account anyway.
Re: Setting up OpenClaw on a cloud VM
#24Are prompt injections solved? If OpenClaw is only useful when it has access to your digital life, then why does it matter where it runs? You might as well be asking me to keep my dead man's switch safely on the moon. If you find this software useful, you are sharing a count down to a no good very bad day with everyone else who finds it useful. One zero day prompt injection technique, your e-mail on a distribution lis…
IDGI. It is reading emails, which is a vector for prompt injection. It is also reading emails, which is where all password resets are sent to. Anyone granting even read access to their primary email is playing with fire.
I personally don't see how the daily briefings or whatever are worth the risk.
Re: Setting up OpenClaw on a cloud VM
#25Your AI should not be in a position to submit a resignation email or send a text to your partner asking for a divorce.
As long as the email or text includes the disclaimer "generated with the assistance of artificial intelligence" then you should be fine.
You forgot the /s... at least I hope you did.
Re: Setting up OpenClaw on a cloud VM
#26Your AI should not be in a position to submit a resignation email or send a text to your partner asking for a divorce.
As long as the email or text includes the disclaimer "generated with the assistance of artificial intelligence" then you should be fine.
It is a charming solution that addresses the optics with great efficiency while leaving the rot entirely undisturbed. By all means, let us proceed if the goal is to feel busy. But when the inevitable occurs, please ensure you have a second, more serious suggestion ready.
Disclaimer: generated with the assistance of artificial intelligence
Re: Setting up OpenClaw on a cloud VM
#27It's really not that hard to run them in docker. Can give them a nestybox (with a little work) sidecar so they can run docker-in-docker. As far as permissions, the only mental model that makes sense to me is treating them like actual people. Bound their permissions in the other systems not on their own machines, basically zero trust. For instance for email, most mail apps have had delegated permissions for a while, e…
You still have to trust your executive assistant. I would never give someone I don't trust the ability to read and write emails for me.
If this takes off, I wonder if platforms will start providing API tokens scoped for assistants. They have permissions for non destructive actions like reading mails, flagging important mails, creating drafts, moving to trash, but not more.
Re: Setting up OpenClaw on a cloud VM
#28most people want openclaw to access their personal files, thats the big use case.
Re: Setting up OpenClaw on a cloud VM
#29Your AI should not be in a position to submit a resignation email or send a text to your partner asking for a divorce.
As long as the email or text includes the disclaimer "generated with the assistance of artificial intelligence" then you should be fine.
but if that disclaimer means that you have to verify whether or not the "sender" agrees with the content that defeats its purpose, no? if we are all going to be like "did you mean to send this text/email...?"
Re: Setting up OpenClaw on a cloud VM
#30serious question why anyone on hn would run this?
For me at least its an interesting project I can take apart and build on top of. I've built 100% my own agent frameworks from scratch and have learned a lot from them. There is something to be said on learning from others projects as well, also because its an ever evolving project with so many contributes whatever fork you go with of your own, theirs a good chance the new goodies will work with your own modified version. For example I'm looking in to LCM right now, and woo-dent you know it someone ported it to openclaw. But nanobot doesn't have it, so I'm considering working on the LCM port to that. If i succeed i will learn a lot and also contribute to progress in my own little ways.