-
-
Notifications
You must be signed in to change notification settings - Fork 14.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
nobody/nogroup shouldn't be used #55370
Comments
See #31990 for syncthing |
Can nixos tests be excluded from this list? Also, the command-fu to regerate this list would be appreciated. |
Also worth mentioning that this list isn't exhaustive as when a group isn't specified in some cases |
If we look at
I have updated the original post with the grep invocation. |
Correct, something like will help: sudo grep ' 65534 ' --files-with-matches /proc/**/gid_map |
I guess this was closed in error @Mic92? |
@peterhoeg yes, it was closed by a merged pull request. |
Sounds like |
More instances: #119559 |
I think there are potentially even more instances.. If a service has a user without a group it also runs as nogroup. |
I updated the list. After #126289 and #133166 a bunch of (old) offenders have been unmasked, so the count went up a bit. Most of these modules should be fixed by switching to systemd I think we should consider adding an annoying warning (learning from my |
One does now actually get a warning on master if a user is missing a group. I think this should solve this issue here as modules no longer evaluate otherwise. |
There are more way more cases than a system user missing a group:
This should not be closed, yet. |
Next to some systemd unit hardening, the nobody user isn't used anymore, as suggested in NixOS#55370.
Next to some systemd unit hardening, the nobody user isn't used anymore, as suggested in #55370.
Next to some systemd unit hardening, the nobody user isn't used anymore, as suggested in NixOS#55370.
Issue description
The problem with
nobody/nogroup
is that people expect them to be nobody while in fact they are somebody named nobody. And that somebody is then shared among all services using it.Their only legitimate purpose is for NFS.
Here are all the files mentioning either - let's get them knocked off!
Generated as follows:
The text was updated successfully, but these errors were encountered: