201–210 of 317 posts
That's why I don't turn memory on. (Claude Code too though for a different reason.) After all the current memory system is too crude to be useful anyway.
Earlier quoted context omitted.
That's because sandboxing is quite hard. I use `cco`, but even then, the home folder is exposed. You are one prompt away from the agent sending the browser passwords with curl. To prevent this, you need a fake home and a networking whitelist for the agent to access the provider (llama cpp, OpenAI, etc.) There is no cross-platform solution that is easy to use for this. And no, a Linux box with Docker won't do. I devel…
Sandboxing is a VERY HARD problem. I've been working on it for months, and finally have something that's mostly there: - Sandbox on Linux using Docker, Podman, containerd, gVisor, Kata, Firecracker - Sandbox on Mac using Docker (Docker Desktop or Orbstack), Podman, Apple containers, Seatbelt, Tart (Tart lets you run simulators). - Network control - Secrets control (file mounts or credentials broker) - NO ambient data…
if it messes up: - no sensitive data is there, so it doesn't really work for serious dev but it's secure for play time
- roll back and fix is done in 10s with ram snapshot
- dollar loss is $10 when it leaks the api key
Somewhat related, but recently I've setup a site for my friend that is a contractor and I have a form that requests the address, name, email OR phone for contact. What I noticed is that people not only put their exact address into it, but also their full legal name, email AND phone number... Now I believe the biggest threat to personal information exfiltration are the people themselves and there's quite literally not…
Earlier quoted context omitted.
Most programmers and power users install large dependency trees with npm/pip/bundler/... on the same user account as their main browser on a regular basis. Even on Linux where it's easy to create new user accounts. This isn't much different.
Two bads doesn't give you one good.
Yeah, we should do this differently. We should probably also eat healthier and get to the gym more.
Doesn’t surprise me. Yesterday I learned that people run AI agents on their system with full admin rights. No containerisation or anything. Wild. Like we forgot 50 years of computer security overnight.
Earlier quoted context omitted.
It has never been easy to create separate users on Linux, certainly not for tasks where you need to switch between contexts. Docker was amongst the biggest steps forward on this in a long time.
I meant for CLI tasks. Just "adduser" and "sudo -u bash".
And when you want the outputs of that user back to your main user?
And when you want that user to access some shared credentials for external services, but not all?
It’s not the account setup that’s hard, it’s the workflow of spreading a single real-world across multiple accounts.
Off topic, you could write "127.0.0.1 evil.com" to your /etc/hosts and bypass all the cloudflare thing I believe