lspcontainers.nvim
firejail
Our great sponsors
lspcontainers.nvim | firejail | |
---|---|---|
8 | 139 | |
294 | 5,429 | |
2.0% | - | |
4.8 | 9.7 | |
4 months ago | 7 days ago | |
Lua | C | |
Apache License 2.0 | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lspcontainers.nvim
-
Are the LSPs secure?
Here is the plugin: https://github.com/lspcontainers/lspcontainers.nvim
-
Looking for devcontainer solution in neovim
lspcontainers/lspcontainers.vim
-
I have just published nvim-dev-container plugin
It's not the same, but you might be interested in looking at https://github.com/lspcontainers/lspcontainers.nvim, which also deals with running LSPs in containers.
-
Good resource for setting up neovim for a 20++ year Vim user?
The third alternative is lspcontainers. Runs the language server process in a docker/podman container, which I think is fantastic.
-
Has anyone had success using lsp-ws-proxy?
You may want to check https://github.com/lspcontainers/lspcontainers.nvim maybe this is a better idea.
- Thoughts on improving security of Neovim plugins
-
Vim users, what additional plugins do you use with vim-go?
I use neovim with the builtin LSP and treesitter. With the lspcontainers plugin I run my langauge server in a docker container and I am very happy with my setup.
-
Pyright, imports and docker
https://www.reddit.com/r/neovim/comments/jiocib/neovim_lsp_and_docker/ https://github.com/lspcontainers/lspcontainers.nvim https://github.com/lspcontainers/lspcontainers.nvim
firejail
-
Sandboxing All the Things with Flatpak and BubbleBox
bubblewrap is designed as a low-level too. There is nothing quick and dirty about it. It disallows everything by default and you have to be explicit about what you want to share with the host. If your application needs complex permissions/resources, then you will need to have a complex bubblewrap command line.
Once you have figured out which permissions/resources you need for a given program, you can wrap the command line invocation in a shell script.
If you want other people to do the work of defining permissions/resources, then have a look at firejail: https://github.com/netblue30/firejail
-
Ask HN: What are some unpopular technologies you wish people knew more about?
Firejail is cool: https://github.com/netblue30/firejail
Linux namespaces/cgroups but nowhere near as heavy as Docker.
I use it when I want to limit the memory of a Python script:
```
-
Toolship: A (More) Secure Workstation
Firejail can also be a useful option, though no good if you're on Mac https://firejail.wordpress.com/
Uses the same Linux primitives as docker etc, but can be a bit more ergonomic for this use case
-
Firejail: Light, featureful and zero-dependency security sandbox for Linux
Firejail, Flatpak (which uses Bubblewrap under the hood), and Snap (which uses AppArmor) all use the same underlying technology: Linux namespaces.
This question comes up a lot, and has been answered here: https://github.com/netblue30/firejail/wiki/Frequently-Asked-...
TL;DR: Firejail has much more comprehensive features than Flatpak (Bubblewrap). Firejail also has more comprehensive network support, support for AppArmor and SELinux, and easier seccomp filtering.
Compared to Snap (which uses AppArmor), Firejail is compatible with AppArmor and again goes above and beyond with a lot of additional features.
-
Bubblewrap – Low-level unprivileged sandboxing tool used by Flatpak
Wonderful little tool, too bad you must chain various exec calling tools to get cgroups (a bit akin to `ionice ... nice ... cmd`) and Linux users namespaces can't allow UNIX sockets while preventing network access (I think?).
Migrated from Firejail when its complexity annoyed me too much and I hit https://github.com/netblue30/firejail/issues/3001 (Firejail doesn't like parens or brackets in --put/--get parameters) to a badly NIH version using bwrap and bash to have "profiles":
- Firejail: Light featureful and zero-dependency security sandbox for Linux
-
Do, or do not. There is no try
Firejail does this. The profile database is the two "profile" directories in https://github.com/netblue30/firejail/tree/master/etc
-
Strange times make for strange friends...
What do you mean by a Firefox container? Do you mean FireJail?
What are some alternatives?
nvim-remote-containers - Develop inside docker containers, just like VSCode
bubblewrap - Low-level unprivileged sandboxing tool used by Flatpak and similar projects
lsp-ws-proxy - WebSocketify any Language Server
flatpak - Linux application sandboxing and distribution framework
cscope_maps.nvim - For old school code navigation. Adds cscope support to Neovim 0.9+.
bubblejail - Bubblewrap based sandboxing for desktop applications
telescope-zoxide - An extension for telescope.nvim that allows you operate zoxide within Neovim.
Flatseal - Manage Flatpak permissions
cutlass.nvim - Plugin that adds a 'cut' operation separate from 'delete'
yabai - A tiling window manager for macOS based on binary space partitioning
nvim-go - A minimal implementation of Golang development plugin for Neovim
podman - Podman: A tool for managing OCI containers and pods.