mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2948] /usr/local/bin/dirname apparmor issue #1842
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#1842
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 @adrelanos on GitHub (Sep 7, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2948
Tor Browser 8.5.5 with firejail and https://github.com/Whonix/apparmor-profile-torbrowser
Does not happen without firejail.
There is no such file /usr/local/bin/dirname. There are no files in /usr/local/bin.
Why does firejail try to execute something form that folder? Avoidable? Could you fix that apparmor issue in a generic way somehow?
Perhaps similar solution as for https://github.com/netblue30/firejail/issues/2947?
@Vincent43 commented on GitHub (Sep 7, 2019):
I don't know the reason of this specific issue but you may reconsider if it does make sense running app with both firejail and custom tailored AppArmor profile. It will get you troubles like that and security benefits will be mostly redundant.
@adrelanos commented on GitHub (Sep 21, 2019):
Do you agree with this sentiment? @netblue30
@Vincent43 commented on GitHub (Sep 21, 2019):
To clarify,
/**/*-browser/Browser/firefoxis your app AppArmor profile which blocks firejail execution. To fix it you would need to weaken this profile. This is exactly I pointed out in https://github.com/netblue30/firejail/issues/2947#issuecomment-529116717 . By trying to use both AppArmor app specific profile with firejail you decrease overall security, not improve it.@Vincent43 commented on GitHub (Sep 22, 2019):
Closing as it's essentially duplicate of https://github.com/netblue30/firejail/issues/2947 and makes discussion fragmented.