3 ms·
This is obviously cool and useful so kudos, but wow security researchers have to throw their hands up all the time. Now we open another attack surface where yo
by zurfer 2mo ago
This is obviously cool and useful so kudos, but wow security researchers have to throw their hands up all the time.
Now we open another attack surface where you can ask a remote agent to do things by default. There was a time when you call this a Remote Code Execution vuln. It's of course a feature here.
- bsian 2mo agoNo, we have always called this RPC or IPC.
- deleted 2mo ago[deleted]
- nizbit 2mo agoMaking calls across a trust boundary, what could go wrong?
- fragmede 2mo agoIt's Claude code talking to another Claude code. They're both already leaking your data to Anthropic in the first place.
- pixel_popping 2mo agoPretty much nothing with minimum viable guardrails (restricted shell into Container into MicroVM into VM + Firewall) which any dev knows how to setup, the fact that most don't is mostly about lazyness/recklessness. Ready for the downvotes.
- smileybarry 2mo agoRemote Control requires (relatively) manual pairing per session and setting the controlling session as trusted, even if the controlling session is a web browser. You can enable a more well-encompassing remote control "server" mode, but it requires extra configuration that isn't (at least clearly) visible in the app itself.