mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #1729] Frequent permission errors with firejail #1169
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#1169
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 @ghost on GitHub (Jan 13, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/1729
While working with firejail I often see my apps(steam, wine stuff) to crash due to permission errors. From the outside I own the files but when I enter the sandbox with bash I can see that a lot of files and folders randomly are owned by 'root' or 'nobody'. I've never ran firejail with root or changed the owner of these containers. This is a fatal error because I can't change the owner from the inside so, I need to delete the files.
I've seen the errors happening from 0.9.44 to 0.9.52 on arch and manjaro too.
@chiraag-nataraj commented on GitHub (Jan 13, 2018):
Can you give a minimum working example? When I try
firejail bash, I get put back in my home directory with all of the files owned by me. When I tryfirejail --private-home=Downloads(as an example), I get back a new home directory with all of the files owned by me.What profile(s) do you see this with? Maybe there's something in common with all of them that will help us figure out what's going on.
@ghost commented on GitHub (Jan 13, 2018):
This won't happen on first try! firejail does work properly for me most of the time. I'm using steam and steam+wine in firejail and this is a once-in-a-month issue. I don't know what triggers it.
@chiraag-nataraj commented on GitHub (Jan 13, 2018):
Hmm, darn. And you only see this in one profile? Or is that the only profile you (regularly) use?
@ghost commented on GitHub (Jan 13, 2018):
No, I've had this happen with multiple profiles(folders) with the steam and wine profiles. I usually need to delete most of the files because I can't use them anyway.
@chiraag-nataraj commented on GitHub (Jan 13, 2018):
I see. To clarify, the first "profiles" ("multiple profiles") refers to Steam profiles, right? (I don't really use Steam, so I have no idea how the terminology works).
What do you mean? Which files? The profiles firejail installs?
@ghost commented on GitHub (Jan 13, 2018):
This won't happen on first try! firejail does work properly for me most of the time. I'm using steam and steam+wine in firejail and this is a once-in-a-month issue. I don't know what triggers it.
@Fred-Barclay commented on GitHub (Jan 13, 2018):
Do you ever do something like
sudo steamorsudo wine? (Orsudo firejail steamorsudo firejail wine, for that matter?)@ghost commented on GitHub (Jan 13, 2018):
@chiraag-nataraj by profile folder I mean I use steam like this:
firejail --private=~/.apps/Steam steamand wine+steam like this:firejail --private=~/.apps/Wine wine ".wine/dosdevices/c:/Program Files/Steam/Steam.exe". So the profiles are folders containing 'faked' home folders.@chiraag-nataraj commented on GitHub (Jan 13, 2018):
@trialism Ah okay, that makes more sense. Which files get weird permissions? The files in those folders? Other random files?
@ghost commented on GitHub (Jan 13, 2018):
@Fred-Barclay never, I don't use sudo and I only use the root account with pacman and to edit files which require a privilege. I always run firejail with the desktop icons, unless it doesn't start then I start a new terminal for debugging.
@ghost commented on GitHub (Jan 13, 2018):
@chiraag-nataraj it's random I guess. For example with this case:
.bash_history,.nv,.wineand the parent dir..are owned by 'nobody' and the rest is on my user.@chiraag-nataraj commented on GitHub (Jan 13, 2018):
So the parent dir being owned by 'nobody' makes sense. But the rest does not. @netblue30, any idea why this might happen?
@chiraag-nataraj commented on GitHub (Sep 28, 2018):
@trialism Is this still an issue for you?
@ghost commented on GitHub (Oct 4, 2018):
@chiraag-nataraj I don't use firejail anymore.
@jcaesar commented on GitHub (Apr 14, 2019):
It's still an issue for me. I can reproduce it by running
firejail --private=$HOME/.bla, then running weechat in there, exiting weechat and the shell in the jail, and then entering the jail again.@chiraag-nataraj Can I ask you to reopen this?
([Edit:] It is possible that my problem is a different one / lack of understanding of the docs. I've moved the .weechat directory in the private directory to a different name and the permission was fixed.)
@rusty-snake commented on GitHub (Apr 14, 2019):
Can reproduce with e.g ghostwriter.
$ normal shell
% shell in FJ
@jcaesar also with
firejail --private=$HOME/.bla --noprofile?It looks like only files that have been blacklisted (in
disable-common.incordisable-programs.inc) are affected. To fix, use--noblacklistor for example with weechatfirejail --private=$HOME/.bla --profile=/etc/firejail/weechat.profile.@jcaesar commented on GitHub (Apr 14, 2019):
@rusty-snake Using the weechat profile indeed fixes the permission. (My firejail has no
--noblacklist.) So maybe it's a different bug than the one @trialism saw.@rusty-snake commented on GitHub (Apr 14, 2019):
@jcaesar I think your FJ has
--noblacklist, but maybe we'll just talk a little bit past it, I meant that you--noblacklist=PATH(where PATH are the files with permission error / See man firejail for --noblacklist).@rusty-snake commented on GitHub (Apr 14, 2019):
Because of the
nobodyandrootthis sound for me it sounds like blacklisting to me.@jcaesar if it was only that :) I would close again.
@jcaesar commented on GitHub (Apr 15, 2019):
Ah, the error message confused me.
So yeah, please close.