You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can tell that the sandbox is working to an extent, because if I try to go to a parent directory with netrv, I don't see any entries, and I also can't update the Neovim plugins I installed.
As you can see, Neovim is given read-only access to both ~/.config/nvim/nvim-sandboxed.fish (which is the sandboxing script) and the landrun binary:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I'm having a hard time trying to mitigate possible sandbox escapes for my Neovim sandbox.
I want to deny access to
~/.config/nvim/nvim-sandboxed.fish, and thelandrunbinary.This is the command I ended up using:
I can tell that the sandbox is working to an extent, because if I try to go to a parent directory with netrv, I don't see any entries, and I also can't update the Neovim plugins I installed.
As you can see, Neovim is given read-only access to both
~/.config/nvim/nvim-sandboxed.fish(which is the sandboxing script) and the landrun binary:But despite that, I can still write to all files in the directory Neovim was launched in, including the
landrunbinary and the sandboxing script.Here are the logs that I get when I start Neovim with the
--log-level debugargument passed tolandrun:I'm really confused as to what is happening here.
Beta Was this translation helpful? Give feedback.
All reactions