-
Notifications
You must be signed in to change notification settings - Fork 567
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
Warning: user namespaces not available in the current kernel. #9
Comments
I think you already have a Firefox instance running. By default Firefox keeps only one browser process running. When you start a new Firefox process, it looks for an existing one. If one is found, the new process shuts down, and the existing one opens a new tab or a new window. Use -no-remote Firefox option to force a new sandboxed process.
My guess is your first Firefox instance is not running in the sandbox. User namespace needs to be compiled into the kernel. Do a short check: in a terminal you should be able to see the following files: /proc/self/uid_map (user id mapping) |
You were right about having firefox already open. Now the .ssh directory is blocked. Thanks! About the "User namespace", Arch has this turned of in the kernel because of security concerns. https://bugs.archlinux.org/task/36969 Here is the lxc configuration on my Arch machine.
|
I am curious though. How does having user namespace turned off effect firejail? |
Thanks, good to know about Arch. The usual reason to turn it off is the number of bugs and fixes still coming into the kernel for user namespaces feature. The bugs are related to creating a root user in the user namespace. This root user is not fully separated from the real root user. Firejail does not create a root user in the user namespace. I don't think firejail is affected by the problem, but who knows... User namespace is just a supplementary sandboxing feature, firejail will work fine without it. |
I am trying to sandbox firefox but I can still access files that should be blocked like my private ssh key. Is kernel 4 supported?
The text was updated successfully, but these errors were encountered: