mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #440] Unexpected behavior with Steam #316
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#316
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 @alexbakker on GitHub (Apr 16, 2016).
Original GitHub issue: https://github.com/netblue30/firejail/issues/440
When I '--join' the Steam process and list what's in my home directory, it appears I have access to the entire thing instead of what would be expected: only the directories with a noblacklist directive in steam.profile. Firejail works fine for me with other software. Am I doing something wrong here?
The steam.profile I'm using is the same as the default, but I'll paste it here for the record:
I launch Steam with the following command:
firejail --env=LD_PRELOAD='/usr/$LIB/libstdc++.so.6' --env=DISPLAY=:0 /usr/bin/steamAnd here's the output I get:
@netblue30 commented on GitHub (Apr 16, 2016):
Steam uses a regular profile: all the files are available with the exception of blacklisted files, mainly password and encryption files. The blacklisted files and directories are replaced with empty files and directories, read-only and owned by root. So, in your --join session if you try to go to ~/.ssh directory, the sandbox wouldn't let you.
This is different than what we do for browsers, where the home directory is whitelisted, and only a few files are visible. We intend to do something similar for Steam.
@alexbakker commented on GitHub (Apr 16, 2016):
Oh, I see. Misunderstanding on my part then.
Thanks!