mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #513] the UID and GID change to root in the sandbox after firejail exit #362
Labels
No labels
LTS merge
LTS merge
bug
bug
converted-to-discussion
doc-todo
documentation
duplicate
enhancement
file-transfer
firecfg
firejail-in-firejail
firetools
graphics
help wanted
information_old
installation
invalid
modif
moved
needinfo
networking
notabug
notourbug
old-version
overlayfs
packaging
profile-request
pull-request
question
question_old
removal
runtime-permissions
sandbox-ipc
security
stale
wiki
wiki
wontfix
wordpress
workaround
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/firejail#362
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @requiredregistration on GitHub (May 12, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/513
i
firejail --private=DIRto start a firejail shell, i run the application and it creates its dot configuration directory and .bash_history, and when i exit the shell, the configuration directory's and the history file's UID and GID change to root@netblue30 commented on GitHub (May 13, 2016):
What kernel version are you using? Run a "uname -r"
@requiredregistration commented on GitHub (May 14, 2016):
4.5.4
@netblue30 commented on GitHub (May 14, 2016):
Yes, I've seen it before on older kernels, I assumed there is a problem with the kernel. Does it happen all the time? Are you using 0.9.38 or the latest in git?
@requiredregistration commented on GitHub (May 15, 2016):
it happens always and i use git.
@netblue30 commented on GitHub (May 15, 2016):
Create a brand new directory and try it:
I am running on the regular 4.5 kernel from Debian backports:
Is it a kernel you compiled? What distro are you running?
@requiredregistration commented on GitHub (May 16, 2016):
the directory was never a problem. something is wrong in firejail and/or the kernel.
this is the kernel config.
@requiredregistration commented on GitHub (May 22, 2016):
also, the grsecurity kernel config.
you must first test with all the latest versions of everything, compiling your own builds where required, and using the arch linux distribution for that.
@netblue30 commented on GitHub (May 23, 2016):
I have no idea what's going on, I cannot reproduce it on Debian/Ubuntu. I've seen something similar a long time ago on older kernels, it used to come and go.
@requiredregistration commented on GitHub (May 29, 2016):
test also with and without CONFIG_USER_NS.
@netblue30 commented on GitHub (May 31, 2016):
Try the new version I just released.
@requiredregistration commented on GitHub (Jun 5, 2016):
i tested with 4.5.4 (# CONFIG_USER_NS is not set) and 4.5.5 (grsecurity 4.5.5.201605291201, CONFIG_USER_NS=y).
the problem was not solved with the new version of firejail, and with the grsecurity kernel the result is files and directories with this stat(1):
Access: (0400/-r--------) Uid: (65534/ UNKNOWN) Gid: (65534/ UNKNOWN)@netblue30 commented on GitHub (Jun 28, 2016):
I've just installed Arch and it seems to be working fine.