Execute in parent's user namespace#4
Open
fionn wants to merge 1 commit into
Open
Conversation
Setting PrivateUsers=yes runs the service in a user namespace. However, this provides marginal or zero benefit to a process that runs as root. > If set to a true value or "self", a minimal user and group mapping is > configured that maps the "root" user and group as well as the unit's > own user and group to themselves (from systemd.exec (5)). It also does no harm, but there is a trade-off: this prevents update-motd from running on systems that disable user namespaces (e.g. by setting user.max_user_namespaces to zero). This can be desirable for security reasons, as the ability to create user namespaces has, at least historically, been partially responsible for local privilege escalation bugs. See: https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#PrivateUsers=
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Setting
PrivateUsers=yesruns the service in a user namespace. However, this provides marginal or zero benefit to a process that runs as root that already has capabilities dropped.(from
systemd.exec (5)).It also does no harm, but there is a trade-off: this prevents
update-motdfrom running on systems that disable user namespaces (e.g. by settinguser.max_user_namespacesto zero). This can be desirable for security reasons, as the ability to create user namespaces has, at least historically, been partially responsible for local privilege escalation bugs.See: https://www.freedesktop.org/software/systemd/man/latest/systemd.exec.html#PrivateUsers=