Fix userns_enabled? check for unprivileged_userns_clone #11017
Merged
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.
The
unprivileged_userns_clone
sysctl parameter may not be present on the target system.On Fedora 28 Workstation,
/proc/sys/kernel/unprivileged_userns_clone
is not present (nor isuserns_restrict
), and the system fails open in its absence, allowing unprivileged users to create user namespaces.Prior to this patch, the
userns_enabled?
method would falsely report unprivileged user namespaces as disabled in the event that theunprivileged_userns_clone
sysctl parameter was not present.The Boolean check for a value of
1
was causing theuserns_enabled?
method to incorrectly returnfalse
, ascat /proc/sys/kernel/unprivileged_userns_clone
was returningcat: /proc/sys/kernel/unprivileged_userns_clone: No such file or directory
.