mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #810] disable-common.inc noblacklist bug #552
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#552
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 (Sep 25, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/810
Hello, after updating from 0.9.38.2 to 0.9.42 (Gentoo), Firejail couldn't work even with the simplest program.
When commenting
in
/etc/firejail/disable-common.inc, I get what I wantNote that it only happens to my "sandbox" user, and only when using a separate X, not through su. This may have to do with the fact that this user is not in the wheel group.
@netblue30 commented on GitHub (Sep 25, 2016):
So basically you are saying that in order to do "echo a" you need /bin/sudo to be available in the filestystem? Try to find out which of the lines you commented out is creating the problem.
@ghost commented on GitHub (Sep 25, 2016):
Maybe I've not been clear, but leaving any of these lines uncommented makes the failure appear (makes me think the noblacklist feature has a problem, actually). By the way,
--debugbrings nothing.@ghost commented on GitHub (Sep 25, 2016):
Managed to pinpoint even more. The lines are uncommented here (as shipped).
@netblue30 commented on GitHub (Sep 26, 2016):
There where two bugs reported by gentoo users:
https://github.com/netblue30/firejail/issues/804 - this one seems to be fixed in git
https://github.com/netblue30/firejail/issues/674 - I think this one can be fixed by commenting out "include disable-devel.inc", but I see you don't have it in the profile.
I would say, update to the latest version in git and give it a try. I'll take a look at noblacklist.
@sakaki- commented on GitHub (Oct 3, 2016):
I see the same thing as Q3CPMA (running Gentoo, firejail 0.9.42). Issue only happens with the
busyboxUSE flag set (it is by default) which in turn enablesbusybox-workaroundin firejail's configure step (leading to the inclusion of the five problematicnoblacklistlines at the head of/etc/firejail/disable-common.inc).PS otherwise a very nice program, thank you.
@netblue30 commented on GitHub (Oct 3, 2016):
We have some special functionality for busybox, disabled by default. if you enable it on a non-busybox system, it will probably not work.
@sakaki- commented on GitHub (Oct 3, 2016):
Sounds like the busybox USE flag shouldn't be set by default in the ebuild in that case. I'll file a bug report on Gentoo. Thanks for the response!