-
-
Notifications
You must be signed in to change notification settings - Fork 288
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Request] dont expose /home #184
Comments
You can change bottles permissions with Flatseal |
Thanks, tried to remove |
It might be interesting but at the moment I want to focus on the main purpose of bottles and the development of v4, without adding too many other tasks. |
Since wine is often used to run production software instead of just games, this doesn't sound like a sane default configuration. If you would e.g. use bottles for microsoft office support, the applications would be rather useless without access to documents. What could be done though, would be to make bubblewrap a dependency of the project and add a sandboxing gui, applicable to any environment/bottle. Unfortunately, I have no experience with bubblewrap inside a sandbox (although it should be possible since a little bit more than a year ago with recent flatpak versions), and therefore can't estimate how much work this would be. |
Is your feature request related to a problem? Please describe.
When running from flatpak, do not expose /home to protect from malwares
The text was updated successfully, but these errors were encountered: