this post was submitted on 15 Jun 2026
267 points (97.5% liked)
Technology
85602 readers
3817 users here now
This is a most excellent place for technology news and articles.
Our Rules
- Follow the lemmy.world rules.
- Only tech related news or articles.
- Be excellent to each other!
- Mod approved content bots can post up to 10 articles per day.
- Threads asking for personal tech support may be deleted.
- Politics threads may be removed.
- No memes allowed as posts, OK to post as comments.
- Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
- Check for duplicates before posting, duplicates may be removed
- Accounts 7 days and younger will have their posts automatically removed.
Approved Bots
founded 3 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
To be fair, protecting credentials and important data is the company and individual's responsibility. The building blocks to restrict access are there, but are often not leveraged (even by large companies with the ability to invest)
Sandboxing is one of them: Both Codex & Claude's sandboxing is reasonable (sandbox-exec, Linux cgroups & seccomp). Many others are lacking, sometimes deliberately.
I do most coding with Pi these days, and I have it heavily sandboxed. I expose sensitive services via a localhost network service with auth (typically for running scripts outside the sandbox). Reads are limited to the system binaries/libs, nad writes to the project dir & Pi's own dirs. If I choose to give a particular session creds, then I have to be very deliberate. I also force egress traffic through a proxy (just logging for now, but I have plans)