-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Running as non-root #22
Comments
In the Debian package we have a systemd unit with quite some sandboxing and which uses CAP_NET_BIND_SERVICE to support using an unprivileged user: https://salsa.debian.org/md/fort-validator/blob/master/debian/fort.service |
Currently there's no available configuration to do this via args, but that's something that we'll add to our TO-DO list. Thanks @rfc1036 for the example. |
Thanks for the pointer to filecaps, I added it to my ebuild and now it works:
And then htop outputs
Here is the ebuild, in case you have comments: https://git.grifon.fr/alarig/SwordArMor-gentoo-overlay/src/branch/master/net-misc/FORT-validator/FORT-validator-1.1.3.ebuild I will drop the filecaps workaround when the “user-fork” will be released. |
Thanks @alarig for sharing the ebuild! We'll check it out.
And we expect to include this improvement soon. |
Hi,
I tried to make an ebuild (and the associated init file) for FORT, but I don’t see any option to change the user after the binding. If I use the start-stop-daemon, FORT can’t bind to port 323 as it’s less than 1024.
And of course, I don’t want to run FORT as root.
Regards,
Alarig
The text was updated successfully, but these errors were encountered: