@github does the support team ever look at tickets? Your automated response offers suggestions that do nothing but go into a continuous loop if there are login issues.
923 Clawdbot gateways are exposed right now with zero auth (they just connect to your IP and are in)
That means shell access, browser automation, API keys.
All wide open for someone to have full control of your device.
Had Clawdbot check my setup:
- Config shows bind: "loopback"
- External port test: connection refused
(Not exposed)
If you're running Clawdbot, check yours:
bind: "all" means you're on that list
Fix: change to bind: "loopback" and restart.
It takes 10 seconds.
RT for exposure
Clawdbot is awesome 🦞
But I just checked Shodan and there are exposed gateways on port 18789 with zero auth
That's shell access, browser automation, your API keys
Cloudflare Tunnel is free, there's no excuse
RT to save a ClawdBot from getting cooked
ts ai conf launch #4
you may have read my book: Principles of Building AI Agents
well, we wrote a sequel: Patterns for Building AI Agents
about bridging the gap where AI teams stumble
between prototype and production
if you like and share this post we will send you a copy
@v0 absolutely impressed me today. It basically one-shotted a fairly complex prototype. Prior experience had been so-so.
Not only was I shocked at how well it worked, but the people I showed it to were ready to pay for the app.