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'm wondering if anyone has successfully used firenvim with a sandboxed Firefox?
I ran firefox in- and outside of a firejail sandbox and lsof on the nvim process to get some clues about what to whitelist. With sandbox:
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
nvim 3415 d9 cwd unknown /proc/3415/cwd (readlink: Permission denied)
...
and a few dozen more /proc/<PID>/ entries with the same permission denied error when using the sandbox. Without the sandbox, there would be entries including the libraries nvim is linked against, nvim's own binary, a couple dozen unix sockets, and a TCP socket (firenvim uses a WebSocket to do RPC with nvim). This isn't surprising, of course--I'm just not sure what to do about it.
I created ~/.config/firejail/firefox.local with this content:
and this allowed the extension itself to work. I suspect I would need to add private-lib and private-bin so the sandbox can access those, as well as some permissions for the TCP listener...
And before I go down that rabbit-hole, I figured I should see if my approach here is even a good one. That is, my idea here is to run the nvim instance inside the same sandbox as firefox by changing firenvim's shell script from exec nvim to exec firejail --join=firefox nvim. Should I be approaching this differently? Or am I just a couple more whitelists away from success?
The text was updated successfully, but these errors were encountered:
I'm wondering if anyone has successfully used firenvim with a sandboxed Firefox?
I ran firefox in- and outside of a firejail sandbox and lsof on the nvim process to get some clues about what to whitelist. With sandbox:
and a few dozen more
/proc/<PID>/
entries with the same permission denied error when using the sandbox. Without the sandbox, there would be entries including the libraries nvim is linked against, nvim's own binary, a couple dozen unix sockets, and a TCP socket (firenvim uses a WebSocket to do RPC with nvim). This isn't surprising, of course--I'm just not sure what to do about it.I created ~/.config/firejail/firefox.local with this content:
and this allowed the extension itself to work. I suspect I would need to add
private-lib
andprivate-bin
so the sandbox can access those, as well as some permissions for the TCP listener...And before I go down that rabbit-hole, I figured I should see if my approach here is even a good one. That is, my idea here is to run the nvim instance inside the same sandbox as firefox by changing firenvim's shell script from
exec nvim
toexec firejail --join=firefox nvim
. Should I be approaching this differently? Or am I just a couple more whitelists away from success?The text was updated successfully, but these errors were encountered: