mirror of
https://github.com/netblue30/firejail.git
synced 2026-05-15 14:16:14 -06:00
[GH-ISSUE #2667] playonlinux + wine + firejail #1682
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#1682
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 @tinmanx on GitHub (Apr 27, 2019).
Original GitHub issue: https://github.com/netblue30/firejail/issues/2667
Question 1: how exactly would you run firejail with playonlinux when wine is being run by playonlinux? Do you need to also configure the wine executable with firejail if only using playonlinux?
Question 2: @Vincent43 you mention here https://github.com/netblue30/firejail/issues/2219#issuecomment-434025708 that the default profile uses blacklists for wine and should use them if you store important files in various non-standard locations, so for example you would need to blacklist a location such as /media since it wouldnt be included?
Why isnt everything blacklisted by default and only whitelist what you want?
@rusty-snake commented on GitHub (Apr 27, 2019):
firejail playonlinuxis enough. Or after you ransudo firecfgyou can just runplayonlinux.@rusty-snake commented on GitHub (Apr 27, 2019):
In firejail you need to different between noblacklist and whitelist
That would mean that the user muss interact with it so that it's work. IMHO it is better if it work out-of-the-box and the user can interact for more security.
@Vincent43 commented on GitHub (Apr 27, 2019):
It would be nice to use a whitelist for only specific elements by default but wine is quite special - it can run unlimited number of apps and it's hard to predict what they need to access (all XDG dirs at minimum I guess). Still I recommend to use whitelist locally and adjust it for your environment.
@rusty-snake commented on GitHub (Jun 26, 2019):
@tinmanx I'm going to close this for now because of inactivity. Please fell free to reopen if you have more questions.