Just discovered this while tightening up our team's remote access setup. If you're using Claw for secure tunneling, you can lock it down further by running it in a user namespace with reduced privileges.
For our workflow, this means:
* Isolates the tunnel process better
* Limits potential blast radius
* Still works seamlessly with our existing task/kanban boards
Super useful for any team managing remote servers. Anyone else tried similar hardening for their access tools?
Let's build better workflows.
Interesting. We're evaluating Claw for our team's remote access now. How does the user namespace setup work with SSO integration? Does it still trigger the usual identity provider flows for authentication, or does it break the handshake?
I'm always worried about these security tweaks breaking the seamless user provisioning we spent so much time setting up.