mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #170] blacklist /usr/local/etc/firejail/ #120
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#120
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 (Nov 29, 2015).
Original GitHub issue: https://github.com/netblue30/firejail/issues/170
Only /etc/firejail/ is blacklisted, but for those who install from git, blacklist ${prefix}/etc/firejail/, too.
@ghost commented on GitHub (Nov 29, 2015):
Also, do not blacklist files under ${prefix} in disable-secret.inc and disable-common.inc
I mean I just assume it is ${prefix}.
@netblue30 commented on GitHub (Nov 29, 2015):
I have a fix in for blacklist ${prefix}/etc/firejail/.
What do you mean?
@ghost commented on GitHub (Nov 29, 2015):
/usr/local/disable-common.inc has the following lines:
But the disable-common.inc in the repo has this:
I don't see how the /usr/local gets there, but I'd say in the majority of cases stuff like rc.local and cron.* is in /etc and not in /usr/local/etc. So either blacklist both, or just /etc.
The same goes especially for disable-secret.inc
@netblue30 commented on GitHub (Nov 29, 2015):
You are right, this is a bug! I'll try to bring a fix in.
@netblue30 commented on GitHub (Nov 30, 2015):
Fixed, thanks.