mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
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#2057
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 @corecontingency on GitHub (Mar 14, 2020).
Original GitHub issue: https://github.com/netblue30/firejail/issues/3277
Originally assigned to: @smitsohu on GitHub.
Running any program with firejail gives this error and exits:
Nothing is in the journal. Tested it with firejail built from commit
b1d54b042f, the commit directly before pull request #3268 was merged, and everything works fine.Running on Arch with GNOME on Xorg. Running on a btrfs filesystem on the built-in RAID1 support. Maybe it is getting confused about my btrfs subvolumes?
My fstab is here:
https://paste.ubuntu.com/p/XVpR38cHZy/
My root btrfs subvolume (subvolid=5):
https://paste.ubuntu.com/p/8nmpWw3NDK/
@rusty-snake commented on GitHub (Mar 14, 2020):
Confirming with a much more simple setup (ext4 root + xfs home).
@rusty-snake commented on GitHub (Mar 14, 2020):
Could break it down to
noexec ${RUNUSER}in disable-exec.inc.firejail '--ignore=noexec ${RUNUSER}' trueworks.@rusty-snake commented on GitHub (Mar 14, 2020):
read-only ${RUNUSER}is also affected.@smitsohu commented on GitHub (Mar 14, 2020):
Hm, that's an interesting error. Could you do me favor and run
and paste the output here? Thanks!
@ghost commented on GitHub (Mar 14, 2020):
I don't seem to be affected (not sure whether that's a good thing). Running Arch on ext4 shows this for the commands @smitsohu suggested, perhaps it can help throw some light onto this.
@rusty-snake commented on GitHub (Mar 14, 2020):
STR:
sudo dnf install makegit clone --depth=1 https://github.com/netblue30/firejail.gitcd firejail./configure --prefix=/usrmakesudo make installfirejail --profile=/etc/firejail/disable-exec.inc true@rusty-snake commented on GitHub (Mar 14, 2020):
firejail --noprofile --noexec='${RUNUSER}' --debug
findmnt -R /run
@smitsohu commented on GitHub (Mar 14, 2020):
@glitsj16 Thanks for the confirmation, I've used this patch for a couple of weeks, it's been fine for me as well so far.
@rusty-snake Does this work?
firejail --noprofile --blacklist='${RUNUSER}/gvfs' --noexec='${RUNUSER}'@smitsohu commented on GitHub (Mar 14, 2020):
Suspecting either FUSE or SELinux to be the culprit here. The problem is I'm temporarily in a situation where my machine is too weak to set up a VM 😢
I guess I need to revert the merge.
@rusty-snake commented on GitHub (Mar 14, 2020):
Yes.
SELinux would create some logs.
IDK if it is helpfull, but the live-system (e.g. over USB) is enough.
@smitsohu commented on GitHub (Mar 14, 2020):
Thanks. This is FUSE. I'll try to add a workaround.
@corecontingency commented on GitHub (Mar 14, 2020):
Late to the party, but here you go:
firejail --noprofile --noexec='${RUNUSER}' --debug
findmnt -R /run
This does not work for me.
I do not have SELinux installed/enabled on my system, although Apparmor is.
@rusty-snake commented on GitHub (Mar 14, 2020):
Can you try this.
firejail --noprofile --blacklist='${RUNUSER}/gvfs' --blacklist='${RUNUSER}/doc' --noexec='${RUNUSER}'@corecontingency commented on GitHub (Mar 14, 2020):
That worked.
@rusty-snake commented on GitHub (Mar 14, 2020):
temporary workarounds ATM:
git checkout b1d54b042fba798fd54037c403bc188c6ffd9240ignore noexec ${RUNUSER}blacklist ${RUNUSER}/gvfsand other fuse mounts in ${RUNUSER}@Fred-Barclay commented on GitHub (Mar 14, 2020):
Can confirm this is an issue in Debian 10 (kernel 5.4 series from backports).
For my case,
firejail --blacklist='${RUNUSER}/gvfs' <program_name>is good enough...@smitsohu commented on GitHub (Mar 14, 2020):
Could someone confirm it is fixed in
3d35c03907?@smitsohu commented on GitHub (Mar 14, 2020):
For the record: We can always open FUSE mounts with
O_PATH, but we are not always allowed to callfstaton the obtained file descriptor.@corecontingency commented on GitHub (Mar 14, 2020):
Seems to work, at least so far! I opened up several programs, and even a steam game.
Thanks!
@smitsohu commented on GitHub (Mar 14, 2020):
Thanks for the patience everyone, I'm going to improve the fix at a later timepoint (if not someone else does)