mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2207] private-bin broken in weird case #1479
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#1479
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 (Oct 20, 2018).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2207
I will investigate more, but here is the scenario I ran into this:
I'm using Viber with
private-lib. One of the libraries it asks for isqt5, so that gets copied recursively. Qt bundlesqmakeetc with it within the/usr/lib/x86_64-linux-gnu/qt5/subdirectory, so that also gets copied. However, since thatqmakeis a symbolic link to/usr/bin/<blah>-qmake,firejailfollows that symlink. When I don't list those binaries inprivate-bin, though,firejailfails with:I thought this was introduced recently, but even the distro version (currently on 0.9.56) has the same issue, suggesting it's been there longer than I realized. The weird thing is that
viberdefinitely was working earlier, so the only thing I can think of that might have caused this is an upgrade of Qt5.@SkewedZeppelin commented on GitHub (Oct 20, 2018):
Potentially related, iirc Viber is no longer developing the Linux client and it is built against like Ubuntu 14.04 or something.
@chiraag-nataraj commented on GitHub (Oct 20, 2018):
Yeah it shows (they base it on
libssl1.0-0, for example). But I didn't have any troubles at all until recently. It seems like the problem is that soemthing inprivate-libpulls in/usr/lib/x86_64-linux-gnu/qt5, which then starts the whole mess. I guess the question is what should happen if something inprivate-liblinks to something in*/bin(asqt5egregiously does) which isn't whitelisted inprivate-bin.@chiraag-nataraj commented on GitHub (Oct 20, 2018):
Getting rid of the offending Qt5 packages seemed to fix this particular bug (so my
viberworks properly now). But we should probably still figure out how to handle this kind of thing.@chiraag-nataraj commented on GitHub (Oct 25, 2018):
From what I can tell, this has to do more with Qt5 putting symlinks to
/usr/bin/in/usr/lib, which, when copied byfirejail(and when those binaries aren't whitelisted inprivate-bin), will throw an error.@SkewedZeppelin commented on GitHub (Aug 1, 2019):
Getting this error with gedit under openSUSE Tumbleweed
with private-lib enabled and private-bin commented it fails
but with private-bin uncommented it works
@ghost commented on GitHub (Jan 20, 2020):
Closing this, should be fixed via
a02d12224b.