Description
netbird is an awesome project, but I'm not a fan of how the client runs with full privileges without any restrictions at all. Not great for a networked service.
With a few systemd features, we can fix this without any modifications to the project's code.
I've been maintaining an unofficial package for Arch Linux. It has most of the isolation flags enabled (have a look at source files at the bottom of the page):
- run the client under an ordinary user (with network capability set — it's not great, but much better than full root)
- most of the FS tree is read-only or not available at all (places like
/home
or/proc
) - netbird cannot load kernel modules, reboot the system, change mount points, etc.
See more suggestions with:
$ systemd-analyze security netbird
Ideally the default socket path should be changed to /var/run/netbird/netbird.sock
because /var/run
typically can only be written by root, and systemd can prepare a subdirectory for you with an appropriate owner (see the patch on AUR). On non-systemd systems it can be created by the installation script.
Any interest in adding something like this to the official .service
so more users benefit from it?