mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #972] security profile is being read twice under certain circumstances #661
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#661
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 @djfd on GitHub (Dec 12, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/972
Hi,
loading app with
--x11=xpraand implicit--profilespecification causes double reading (and applying) security profileperhaps for a double security ))
there is a command line to reproduce
@netblue30 commented on GitHub (Dec 13, 2016):
The first reading just loads the profile into memory, it doesn't process it. I'll disable the reading.
@djfd commented on GitHub (Dec 13, 2016):
hmm, not applied you say...
did you see that all disables are done 4x times? why is that then?
yet another question. how do xpra client/server launched? with or without sandbox? is there any security threats if/when started as regular user?
I noticed that there is some dbus magic in xpra, can this be used eg. to escape from the sandbox if client/server are both trusted?
@pyamsoft commented on GitHub (Dec 19, 2016):
Because you are on Arch, every binary location, /usr/sbin, /bin, and /sbin are symlinked to /usr/bin.
firejail still processes these locations, but only actually disables the real binary located in /usr/bin.
@djfd commented on GitHub (Dec 19, 2016):
yeah, I know
But it is at least confusing, is not it? I really dislike to see that my /bin directory is being protected 4x(!) times...
I agreed, it is just small cosmetic issue, but it is here...
Until the bug is documented it is a bug, after being documented it is a feature. Do you feel a difference?
@pyamsoft commented on GitHub (Dec 19, 2016):
Yes I agree with you it can be confusing. I just wanted to convey that, due to the set up of your system, it was purely a cosmetic issue you were experiencing, and should not affect the security of firejail itself.
@chiraag-nataraj commented on GitHub (Jul 30, 2018):
Seems to be fixed in the current version (it still lists things twice since
/bin -> /usr/binon my system, but it describes why it's listed the second time).