mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #333] [enhancement] Better handle symlinks in /usr/bin #237
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#237
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 @chiraag-nataraj on GitHub (Feb 28, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/333
Right now, private-bin's behavior when it comes to symlinked binaries is less than ideal - for example, firefox will refuse to start with "Unable to find Mozilla runtime" and libreoffice just doesn't start (not many error messages). Both of these issues have to do with the fact that when you whitelist symlinked binaries, the symlinks aren't copied as-is - instead, the linked binary itself is copied. Copying the symlink itself would solve the problem, at least with those two programs.
@chiraag-nataraj commented on GitHub (Feb 28, 2016):
I understand that technically this may break the symlink (say, if the symlink is to a blacklisted directory), but that should be up to the user to figure out/manage (and shouldn't happen in the vast majority of cases anyway).
@netblue30 commented on GitHub (Mar 20, 2016):
Fixed!
@chiraag-nataraj commented on GitHub (Mar 21, 2016):
Awesome! Thanks!