Repository navigation
|
Hi, I know I can I'm already using nono in a separate limited user account, so the home directory doesn't have anything secret for now. I'm trying to switch to nono on my macos system. I had some ideas, like
But I was wondering if others have a better way. |
Replies: 2 comments 2 replies
|
The closest thing to your bwrap setup is a small profile that grants a separate directory and points
{
"meta": { "name": "sandbox-home" },
"extends": "default",
"workdir": { "access": "readwrite" },
"filesystem": { "allow": ["$HOME/sandbox-home"] },
"environment": { "set_vars": { "HOME": "$HOME/sandbox-home" } }
}mkdir -p ~/sandbox-home
cd not-home
nono shell --profile sandbox-home --allow-cwd
# inside the shell
curl -fsSL https://get.pnpm.io/install.sh | sh -
source ~/.zshrc
pnpm env use --global lts
pnpm add -g @earendil-works/pi-coding-agentI ran this on 0.81.0 on an arm64 Mac, with Your two ideas don't get there. Two things that caught me. Don't pipe |
|
Thanks, that works, but is there a way to use the original home dir? Running install commands inside nono isn't common? |
Yes, on macOS there is an option I missed above:
allow_parent_of_protected. Without it, a grant that contains nono's state dir is refused. With it, nono allows the grant and adds Seatbelt deny rules for~/.nonoand$XDG_STATE_HOME/nono, so the state stays protected. It's documented in the profile authoring guide (section "Allowing parent-of-protected-root grants (macOS only)") and ignored on Linux, where Landlock can't deny a child of an allowed parent.{ "meta": { "name": "real-home" }, "extends": "default", "allow_parent_of_protected": true, "workdir": { "access": "readwrite" }, "filesystem": { "allow": ["$HOME"] } }I ran this on 0.81.0 (arm64 Mac,
HOMEpointed at a throwaway…