Skip to content
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

Security Implications for User namespaces #425

Closed
HulaHoopWhonix opened this issue Apr 10, 2016 · 3 comments
Closed

Security Implications for User namespaces #425

HulaHoopWhonix opened this issue Apr 10, 2016 · 3 comments
Labels
information_old (Deprecated; use "doc-todo" or "needinfo" instead) Information was/is required

Comments

@HulaHoopWhonix
Copy link

User namespaces are described as a particularly risky kernel feature that has allowed privilege escalation in the past. I think its useful to keep around but its probably best avoided in supported profiles.

subgraph/oz#11

@netblue30 netblue30 added the information_old (Deprecated; use "doc-todo" or "needinfo" instead) Information was/is required label Apr 10, 2016
@netblue30
Copy link
Owner

User namespace is more like a baseball bat. Imperfect, with its own problems, but works very well in some cases.

Firejail has support to disable various sandboxing features the user might find undesirable. You can do it at compile time (./configure --help) or at run time (man firejail-config). You can disable user namespaces, chroot, and a number of other features. So far I've heard complains about user namespace and networking.

@curiosity-seeker
Copy link
Contributor

FWIW, user namespaces are not supported by Arch Linux, either, because of security considerations.

@HulaHoopWhonix
Copy link
Author

Ah OK. You're aware of this topic: and discussed implications: #9 (comment)

I'll search harder next time :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
information_old (Deprecated; use "doc-todo" or "needinfo" instead) Information was/is required
Projects
None yet
Development

No branches or pull requests

3 participants