Elektrine lite

← Feed

@rachelplusplus@tech.lgbt

Post #2551115

2026-05-12 07:50 UTC

RE: https://digipres.club/@misty/116558924676616687 Things like this seem to be increasingly common, and I've been thinking a lot about how to avoid getting pwned myself, without retreating into "trust nobody, write everything from scratch" because that isn't helpful either. I've already split my dev work off into its own VM to minimize the escalation surface to my main user account. But I'm considering splitting things further into two user accounts: One which gets everything needed to write code (read-write access to repositories, SSH keys, etc.) and a separate build account which has read-only access to repositories and very little else. Idea is that a compromised build account shouldn't be able to write anywhere that the code-writing account can exec from, to make it harder to escalate from one to the other

Replies (1)

  • @amenonsen@flipping.rocks 2026-05-12 08:05

    @rachelplusplus@tech.lgbt Reminds me of the Qubes OS approach (which I vaguely knew about, but found more compelling only after someone I know tried it a year or so ago and posted on his blog about how he manages his own work… but now I can't find the post).

    Open ##4295655